Install Flint on your Mac.

1. Download the beta

Use the download form on the home page and enter the six-digit code sent to your email. The verified download link is short-lived, and the DMG itself is versioned so published builds are never silently replaced.

2. Approve the first launch

1. Open the DMG and drag Flint into your Applications folder.
2. Open Flint once. When “Flint Not Opened” appears, click Done—do not move Flint to Trash.
3. Open System Settings → Privacy & Security, scroll to Security, and click Open Anyway for Flint.
4. Enter your Mac password and confirm Open. Flint can then launch and request its normal permissions.

Open Anyway is available for a limited time after the blocked launch attempt. If it is missing, try opening Flint once more and return to Privacy & Security.

3. Complete local setup

Onboarding requests Microphone and Accessibility access, then downloads your selected speech model. Accessibility covers Flint's shortcut listener as well as text insertion, so a separate Input Monitoring grant is not required. Once the model is ready, dictation and personalization work without an internet connection.

You can run setup again at any time from the menu bar: Flint → Run Onboarding Again. Existing models, vocabulary, and permissions are preserved.

Remove Flint and its models

Before removing the app, open Flint from the menu bar, choose Privacy, then select Uninstall Flint. Flint deletes downloaded speech models and its other local data, disables Launch at Login, moves Flint.app to Trash, and quits.

Dragging Flint.app directly to Trash cannot notify the running app or remove its files from your Library folder. If you already removed Flint manually, open Finder → Go → Go to Folder and enter ~/Library/Application Support/Flint, then move that Flint folder to Trash to reclaim the model space.

What is in 0.1.0-beta.12

• Escape now passes through normally unless an active dictation is being cancelled.
• This build keeps the same private beta identity as Beta 11, so its macOS permission identity is unchanged.
• Gatekeeper still shows the expected unverified-app warning because this beta is not Developer ID signed or notarized.

SHA-256: 72dfa326f6086c6694906a375bd3deb705060b132809f6e177ddc13ae4745823