Most AI writing tools still assume the same workflow:
- Stop writing
- Copy the sentence
- Open a browser tab or side panel
- Ask for a rewrite
- Read three versions
- Paste one back
- Fix the tone so it sounds like you again
That is fine for long documents. It is terrible for everyday writing.
The highest-friction writing is usually not a polished essay. It is the sentence inside the app you are already using:
- a GitHub comment
- a Linear ticket
- a Slack message
- an email reply
- a support response
- a changelog note
- a product update
- a docs paragraph
For those moments, the expensive part is not generating text. The expensive part is breaking flow.
The real problem is context switching
When writing help lives in a separate tab, it becomes another task.
You have to decide what to copy, decide how much surrounding context to include, ask for a rewrite, inspect the output, then move it back into the original field.
That sounds small, but it changes the psychology of the tool. Instead of being a writing assist, it becomes a writing detour.
For developers and technical writers, that matters. Most of the writing we do is embedded inside another workflow. We are not opening a blank page to write prose for its own sake. We are explaining a bug, clarifying a decision, answering a teammate, documenting a behavior, or turning a messy thought into something shippable.
If the tool pulls you away from that surface, it is already costing attention.
Autocomplete and rewrite should be close to the cursor
The best version of AI writing help on a Mac is boring:
- suggest the next phrase when I am already typing
- rewrite the selected text when I ask
- stay out of the way when I do not need it
- work in normal macOS text fields where possible
- avoid turning every small edit into a chat session
That is the key difference between "AI as a destination" and "AI as an input layer."
A chat window is a destination. You go there, ask for something, then bring the result back.
An input layer is different. It helps at the point of writing. The cursor stays where the work is.
Local AI matters more for writing than people admit
Writing often contains sensitive fragments even when the whole document is not secret.
A half-written email can include names, plans, customer context, private opinions, internal wording, or unreleased product details. A bug report can include implementation details. A support reply can include personal information. A journal note can be private by default.
Cloud AI tools are useful, but a lot of everyday writing assistance should not require sending text somewhere else just to clean up a sentence.
Local AI is not always the right answer for every task. Big cloud models are still useful for heavy reasoning, research, or large drafts. But for quick autocomplete and instruction-based rewriting, local-first is a strong default because the text does not need to leave the machine for small edits.
There are honest Mac limitations
This is also where Mac writing tools need to be honest.
System-wide text help is not magic. macOS apps expose text fields differently. Some fields work cleanly through Accessibility APIs. Some custom editors expose less context. Some web apps behave differently depending on the browser, editor, and focus state.
A good Mac writing assistant should not pretend every text box is identical. It should work where macOS allows it, explain the limits, and avoid making privacy claims that depend on hidden server behavior.
That is the product shape I want more of: native, local when possible, close to the cursor, and honest about what the operating system allows.
What I am building
I am working on DraftKey, a native Mac app for private on-device AI autocomplete, instruction-based rewriting, and mechanical keyboard typing sounds in existing macOS text fields.
It is for people who want writing help without turning every sentence into a browser-tab workflow.
The practical version is simple:
- keep typing where you already are
- use autocomplete when it helps
- select text and rewrite it with an instruction
- keep the local AI work on your Mac
- accept that some text fields will have platform limits
It requires macOS 14+, Apple Silicon, and 8GB memory for AI. The local model download is about 1.12GB.
The direction I think wins
The next wave of writing tools should feel less like separate apps and more like quiet infrastructure.
Not another dashboard.
Not another tab.
Not another place to paste your half-finished sentence.
Just help where the sentence already is.
That is the difference between a tool you admire and a tool you actually use every day.
Top comments (0)