You finally hit your groove. The Slack message is flowing, the investor update is taking shape, the support reply is landing exactly the right tone. Then you need to tighten a paragraph.

So you copy the text. Open a new tab. Navigate to ChatGPT. Write a prompt. Paste. Wait. Copy the result. Switch back. Find your cursor. Paste over the original.

By the time you're done, the groove is gone.

This is the fundamental problem with AI-assisted writing in 2026. The AI is good. The workflow around it is terrible. Every rewrite requires leaving the app you're working in, and every app switch costs you focus you can't easily get back.

This guide shows you how to set up a writing workflow on macOS where AI helps you without interrupting you.

Why Your Current AI Writing Setup Kills Focus

Cal Newport's research on deep work puts numbers to what you already feel: context switching costs anywhere from 10 to 23 minutes of recovery time. Even a "quick" tab switch to ChatGPT introduces a micro-interruption that fragments your attention.

The problem compounds across a typical workday. If you're a marketer drafting campaign copy, a support lead handling tickets, or a developer writing documentation, you might rewrite or rephrase text 20 to 40 times a day. At even 30 seconds per round-trip to an AI chat interface, that's 10 to 20 minutes of raw switching time. Factor in the focus penalty and you're losing over an hour of productive writing time daily.

The root cause isn't AI. It's architecture. Browser-based AI tools require you to leave your writing context. That's the wrong model for something you do dozens of times a day.

The Three Layers of an AI Writing Workflow

A workflow that doesn't break your focus needs three things working together: the right trigger, the right AI, and the right delivery.

Layer 1: A System-Level Trigger

The trigger is how you invoke AI assistance. If this requires switching apps, opening a browser, or navigating to a URL, the workflow is already broken.

On macOS, the gold standard is a global keyboard shortcut. A single key combination that works regardless of which app is in the foreground. You're in Mail? Same shortcut. Notion? Same shortcut. Slack? Same shortcut.

This is fundamentally different from browser extensions or app-specific plugins. Those require per-app installation, break when apps update, and often don't support the app you actually need.

A system-level shortcut means the trigger is always available, always the same, and takes zero navigation.

Layer 2: The Right AI Model (That You Control)

Not all writing tasks need the same AI. A quick email tightening doesn't need GPT-4-class reasoning. A nuanced investor update might.

The ideal setup gives you model choice. Specifically, BYOK -- bring your own key. Instead of paying a writing-tool subscription that locks you into one model, you use your own API key for Claude, GPT, Mistral, or whatever model fits the task.

BYOK has three advantages beyond cost:

  1. Privacy. Your text goes directly to the AI provider's API. No middleman SaaS storing your writing.
  2. Model flexibility. Swap models as they improve. Today's best model isn't tomorrow's.
  3. Cost transparency. You see exactly what you spend per API call instead of paying a flat $20/month regardless of usage.

If you already have a Claude or OpenAI API key for development work, you're halfway there.

Layer 3: Inline Delivery

This is where most setups fail. Even if you trigger AI from a shortcut and use a great model, the result needs to land back in the exact spot you're writing. Not in a sidebar. Not in a separate window. Not in a chat interface you have to copy from.

Inline delivery means: you select text, invoke AI, and the improved text replaces your selection in place. You never leave the app. You never lose your cursor position. The rewrite feels like an undo/redo -- instant and invisible.

Building the Workflow on macOS

Here's how to assemble these three layers into a working system.

Step 1: Audit Your Writing Surface

Before choosing tools, map where you actually write. Open your recent app usage (System Settings > Screen Time > App Usage) and note which apps you spend time typing in.

For most professionals, the list looks something like:

Your AI writing tool needs to work in all of these. If it only works in the browser, you've already lost coverage for native apps. If it requires a plugin per app, you'll inevitably hit an app that's unsupported.

Step 2: Set Up a System-Level AI Rewriting Tool

This is where RewriteCmd fits. It's a native macOS app that lives in your menu bar. Select text in any app, hit Cmd+Shift+R, and AI rewrites the text in place.

Because it operates at the system level using macOS accessibility APIs, it works everywhere -- Mail, Slack, Notion, VS Code, Chrome, Safari, any app with selectable text. No browser extensions. No per-app plugins. One shortcut, every app.

Setup takes about two minutes:

  1. Install RewriteCmd from rewritecmd.com
  2. Grant accessibility permissions when prompted
  3. Add your API key (Claude, OpenAI, or Mistral) in preferences
  4. Test it: select some text in any app, hit Cmd+Shift+R

The BYOK model means there's no AI subscription on top. You use your existing API key and pay per use.

Step 3: Configure Your Rewrite Presets

Raw "rewrite this" isn't always what you want. Different writing contexts call for different transformations:

Set up presets for the transformations you use most. This turns a two-step process (invoke AI + specify what you want) into a one-step process (invoke the right preset).

Step 4: Build Muscle Memory

The biggest productivity gain comes from making AI rewriting as automatic as Cmd+Z for undo. That requires repetition.

For the first week, consciously use the shortcut every time you'd normally copy-paste to ChatGPT. You'll feel the friction of the old habit pulling you toward the browser. Resist it.

By week two, the shortcut becomes reflexive. You'll select text and hit Cmd+Shift+R without thinking about it, the same way you hit Cmd+C to copy. That's when the real productivity gain kicks in -- the rewrite happens in the background of your thought process instead of interrupting it.

Step 5: Eliminate the Remaining Context Switches

Once inline rewriting is habitual, audit what's still pulling you out of your writing apps:

Each of these used to be a separate app switch. Now they're all the same gesture.

Measuring the Difference

After two weeks with this workflow, track the change:

Time saved per rewrite: The old copy-paste-to-ChatGPT workflow takes 30 to 90 seconds per rewrite. Inline rewriting takes 3 to 5 seconds. On 25 rewrites per day, that's 10 to 35 minutes saved in raw execution time.

Focus sessions preserved: More importantly, count how many times you didn't leave your writing app. Each avoided context switch is a focus session preserved. Over a day, that compounds into significantly deeper work.

Writing output: Most professionals report writing 15 to 25 percent more content in the same time window. Not because the AI writes for them, but because they spend less time managing the AI and more time thinking about what to write.

Common Mistakes to Avoid

Over-relying on AI for first drafts. AI rewriting works best on text you've already written. Use it to refine, not to generate from scratch. Your ideas, AI's polish.

Using the same prompt for everything. A Slack message and a board presentation need different treatment. Set up distinct presets instead of one generic "rewrite" command.

Ignoring the output. Inline rewriting is fast, which makes it tempting to accept every suggestion without reading. Always scan the rewrite. AI occasionally shifts meaning or introduces a tone that doesn't fit.

Not securing your API key. If you're using BYOK, treat your API key like a password. Use a tool that stores it securely in the macOS Keychain, not in a plaintext config file.

The Bigger Picture

The professionals who get the most out of AI aren't the ones with the best prompts. They're the ones with the best workflows.

A great AI writing workflow has the same qualities as any great tool: it's invisible when it's working. You don't think about the tool. You think about the writing. The AI handles the mechanical work of rephrasing, tightening, adjusting tone -- and it does it without pulling you out of whatever app you're in.

That's what "doesn't break your focus" actually means. Not that the AI is unobtrusive in some abstract sense. That it literally never requires you to leave the place where you're doing your work.

Set up the workflow. Build the habit. And get back to writing.

Ready to stop context-switching every time you need to rewrite? Try RewriteCmd free -- inline AI rewriting for every macOS app, powered by your own API key.