macOS completion panel that offers the most likely continuation from your own writing history — at the caret, in every app. A frontier model steps in only when you need something genuinely new.
macOS 14 or later · no account · no API keys · memory stays on-device
The continuation you want usually already exists — in a prompt you wrote last week. Local retrieval finds it in milliseconds, offline, for free.
You’ve typed this opening before — the full continuation returns in ~2 ms.
Scaffolds you reuse constantly, recognised with the parts that vary left open.
Everything you’ve written, indexed on-device and ranked against your caret.
Nothing good locally? A frontier model writes something new — visibly, never silently.
Press the key and one to three candidates appear beside your cursor. Your app keeps focus the whole time.
The panel never activates. Your window, cursor, and selection stay exactly put.
One to three strong options. Never fifty weak ones to read through.
Multi-line candidates render readably — built for prompts and prose, not tokens.
Escape, or the hotkey again, dismisses. Nothing is ever inserted without ↵.
Accepting writes the text into the app you were already using — cleanly, safely, in any language.
⌘Z behaves exactly as if you had typed it. The host app is never confused.
Korean, Japanese, and Chinese composition is never corrupted. UTF-16 correct throughout.
A selection becomes the rewrite scope; otherwise it continues from the caret.
Moved the caret while it was thinking? It re-anchors — or does nothing at all.
It learns only from completions you accept. Everything stays on your Mac.
Between invocations nothing runs and nothing watches. That’s the architecture, not a policy.
Your corpus and your accepts never leave the machine. No cloud sync, no upload.
See everything it remembers. Delete any of it. One switch erases all of it.
Offline or provider down — it says so plainly and does nothing.
Password fields and secure input are detected and refused automatically.
It never spends your AI subscription retrieving a sentence you already wrote.
Local retrieval is the core, not a fallback. Planes and tunnels included.
Turn it off in specific apps, or pause everything with one switch.
Completions come back in the language you’re writing — Korean included, at launch.
When the model does run, the panel opens instantly and text arrives progressively.
A native panel on native APIs. No Electron, no browser runtime, no background service.
One plan, every capability. Your price is locked at what you join at.
$20 / month
Billed monthly. Cancel anytime. Price locked for early members.
In development — early access opens with the private beta.
Your own writing history — starting with the prompts you’ve already written to coding agents — indexed on your Mac and searched at invoke time. A frontier model is used only when nothing local is good enough.
No. It reads the focused field only at the moment you press the shortcut. Between invocations nothing runs — that is how it is built, not a promise.
Reading the focused field and inserting text into another app requires it — there is no other macOS API. Password fields and secure input are always refused.
Anywhere macOS exposes the focused text field: browsers, editors, Terminal, Mail, Slack, and native apps. Unsupported fields fail honestly instead of guessing.
Korean is a launch requirement, not a follow-up — IME composition is never corrupted, and offsets are UTF-16 correct across CJK and emoji.
The native layer — panel, capture, safe insertion — is built and tested. The retrieval engine is being proven against real history before anything is sold.