Two taps and it is
already written.
No prompt to type, nothing to say out loud. Put your cursor in any text field, double-tap the hotkey, and your Handler reads what's actually on your screen, works out what you'd write next, and types it there in your voice. You edit it, you send it. It never sends anything itself.
Ghostwriter is part of the desktop app; it reads the screen locally.
Any app: your mail client, Slack, a browser form, a comment box.
Only for the scheduling cross-check — everything else works without one.
Put your cursor where the words go. No prompt, no dictation. Double-tap the hotkey and your Handler captures the screen around that cursor — the thread above it, the question beside it, the half-finished sentence in it.
It works out what kind of writing this is. A reply owed in a thread. A sentence to continue from exactly where it stops. A blank box under a question that wants a real answer. A message the context obviously calls for. Getting that right is most of the job, so it decides before it writes a word. If the reply proposes a time, it is checked against the next two weeks of your calendar first.
The text appears at your cursor. Exactly as written, nothing sent. Read it, change it, delete it, send it — that last step stays yours. Select text first and it rewrites the selection instead.
The whole interaction is a double-tap. You don't describe what you want — that's the point; describing it was the work you were avoiding.
Reply, continue, fill in, or compose from scratch — it identifies which before writing, so a continuation doesn't restate your sentence and a reply doesn't summarise the thread back at you.
It maps each message to its sender, works out which handle is yours, and tracks who asked whom for what — so it answers the other party rather than replying to your own words.
What Ghostwriter reads
When you double-tap, your Handler reads the screen around your cursor — the thread, the form, whatever is in front of you — because that context is the entire input. That capture happens on your machine, against the encrypted vault on your PC.
The assembled context is sent to our cloud model (zero data retention) to write the draft.