for the prose around the code

Autocomplete for developers on Mac — commit messages, docs, comments

You already have Copilot finishing your code. MacAutocomplete finishes everything around it — the commit message, the PR description, the doc comment, the Slack reply — with greyed ghost text in whatever field you're typing in. Local model, Tab to accept, no subscription.

What it actually completes (and what it doesn't)

Be clear about the job: MacAutocomplete predicts natural-language prose, not source code. It is not a Copilot replacement inside your editor's code buffer — it won't finish a function body or infer a type. Where it earns its keep is the writing developers do all day that nobody automates: the commit summary, the PR body, the README paragraph, the doc-comment above a method, the issue you're filing, the Slack message explaining a deploy. That text lives in standard macOS text fields, which is exactly where the ghost text shows up.

Ghost text in your git workflow

Start a commit message in your terminal's editor, a GUI git client, or your IDE's commit box, and the rest is offered inline:

fix: debounce the completion request so rapid keystrokes don't fire a model call on every character.

Press ⇥ Tab or → to take the whole line. Keep typing and it disappears. The accept key is only intercepted while a live suggestion is showing, so Tab still indents and tab-completes normally everywhere else — it never fights your shell or your editor.

Where developers see it

Because it hooks the system text layer rather than one app, the same prediction follows you across the writing tools in a normal dev day: GitHub and GitLab text boxes in the browser, the commit and PR fields in Slack, your linear or Jira issue forms, Notes and Markdown editors, email, and most terminal-adjacent text fields. One install, the same behavior everywhere — see how it works in every app and how it feels for Slack.

Local, offline, and quiet about it

The model runs on your Apple Silicon Mac with MLX. Completions make zero outbound network calls— verify it yourself with Little Snitch. Nothing you type in a private repo, an internal PR, or a customer thread ever leaves the machine, and password and secure-input fields are never read. For a team that can't send code or context to a cloud endpoint, that's the difference between a tool you can install and one legal blocks.

How it fits next to your code tools

Different jobs, no overlap:

One caveat developers hit: editors that paint text onto a canvas — Google Docs and Sheets, some GPU-based editors — don't expose a readable field, so MacAutocomplete stays silent there rather than guessing. Everywhere with a normal text field, it just works.

Frequently asked questions