cd /news/ai-tools/i-wanted-ai-rewriting-to-feel-like-a… · home › topics › ai-tools › article
[ARTICLE · art-140299] src=dev.to ↗ pub= topic=ai-tools verified=true sentiment=↑ positive

I wanted AI rewriting to feel like a Mac keyboard shortcut

A developer built DraftKey, a native macOS app that brings private, on-device AI autocomplete and instruction-based rewriting to existing text fields via a keyboard shortcut, requiring macOS 14+, Apple Silicon, and 8GB of memory with a roughly 1.12GB model download. The app aims to replace the copy-paste-into-a-chatbot workflow for small edits, keeping drafts local rather than sending them to cloud services. The developer notes that macOS text fields vary in how they expose text through Accessibility APIs, so a system-wide assistant must handle those edge cases.

by read2 min views1 publishedSep 27, 2026

If you use AI to clean up writing on a Mac, the annoying part is usually not the model. It is the workflow.

You write something in Mail, Notes, Linear, Slack, a browser textarea, or an editor. Then you copy it into ChatGPT, explain what you want, wait, copy the result back, and check whether formatting survived.

That is fine for a long document. It is clumsy for the tiny edits that happen all day:

For that kind of writing, I think the better interface is a keyboard shortcut. A Mac writing assistant is much more useful when it works inside the text field you are already using.

Select text, hit a shortcut, give a short instruction, accept the rewrite, keep moving. No AI tab. No separate editor. No context switch just to make two sentences sound less awkward.

That interaction matters because most writing work is not "write me a whole article." It is small edits in existing apps.

Cloud writing tools are convenient, but they also ask you to send drafts, replies, notes, or internal work text somewhere else.

For a lot of personal writing, that is not a big deal. For work notes, client replies, unfinished ideas, or sensitive drafts, it can be enough friction that you just avoid the tool. Local AI is not magic, but it changes the default. If the model runs on the Mac, the writing help can happen on-device instead of becoming another cloud copy/paste step.

That is the tradeoff I like for everyday rewriting: a little more local setup, a lot less trust overhead.

macOS text fields are not all the same.

Some apps expose text cleanly through Accessibility APIs. Some custom editors and web apps behave differently. A system-wide writing assistant has to deal with those edge cases instead of pretending every text box is identical.

So I would not judge a Mac AI writing tool only by whether it has the biggest model or the flashiest chat UI.

I would judge it by:

I have been working on DraftKey, a native Mac app for private, on-device AI autocomplete and instruction-based rewriting in existing macOS text fields. It also has optional mechanical keyboard typing sounds, because writing tools should feel good to use, not just be technically useful.

It requires macOS 14+, Apple Silicon, and 8GB memory for local AI. The model download is about 1.12GB.

If you want local AI writing help that stays closer to the text box, it is here: https://www.getdraftkey.com/ The bigger idea is simple: for everyday writing, AI should feel less like opening a chatbot and more like pressing a key.

── more in #ai-tools 4 stories · sorted by recency
── more on @draftkey 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/i-wanted-ai-rewritin…] indexed:0 read:2min 2026-09-27 · —