Select Text and Rewrite With AI: The Hotkey Loop

Once you’ve used a real inline editor, the whole interaction compresses into a reflex: highlight, tap, done. But there’s a precise sequence underneath that reflex, and understanding each beat helps you get more out of it — and helps you spot the tools that fake one of the steps. This is the select → hotkey → rewrite loop, walked through end to end.

[[MISSING: demo GIF — the 3-step loop shown live: messy selection → hotkey → clean rewrite swaps in]]

Step 1 — Select the text

You highlight exactly what you want to change. This is more important than it looks, because the selection is your input. There’s no separate prompt box where you describe the text — you just point at it by selecting it.

A few practical notes:

Step 2 — Press the hotkey

With your text highlighted, you press a global keyboard shortcut. This is the step that makes inline editing feel native: your hands stay on the keyboard, and the shortcut works in whatever app you’re in, not just one.

The hotkey carries the instruction, and there are two ways that works:

Some tools also let a single hotkey pop a small menu of actions, so you press once and pick — useful when you don’t want a key for every job. Either way, the principle holds: the instruction rides with the keypress, so you’re not typing a prompt every time.

Step 3 — The rewrite replaces your text

The editor sends your selection (and, in better tools, a little surrounding context — see Context-aware inline rewriting) to the AI, and the result replaces the original in place.

Three things should happen here, and their absence is how you spot a weak tool:

  1. It streams in. The new text appears progressively rather than after a frozen wait, so you’re never staring at a spinner over your document (Live-streaming AI edits with no frozen cursor).
  2. You see it before you keep it. A diff shows what’s leaving and what’s arriving; you accept or reject. No blind overwrite.
  3. You can undo it. If you accept and then regret it, one keypress restores the original from local history.

That’s the full loop. Select, hotkey, replace — with streaming, a diff, and undo making the third step safe.

Building the muscle memory

The loop becomes automatic fast, but a couple of habits speed it up:

Where the loop breaks (and shouldn’t)

The loop only works if step three is reliable. The common failure is the hotkey doing nothing in Slack, VS Code, Obsidian, or a JetBrains IDE, because the accessibility write misfires in those frameworks. A tool that’s serious about the loop uses a fallback so the replace lands anyway — covered in The anatomy of a reliable inline replace.

The loop, done right, in EditSnappy

EditSnappy is built around this exact loop. Select text in any app, press your hotkey, and the rewrite streams into place — shown first as a diff (Tab to accept, Esc to keep your original), undoable with one key from local history, formatting preserved, and the AI’s preamble stripped. It runs the loop reliably even in Slack, VS Code, and Obsidian where other tools’ step three silently fails, and behaves identically on Mac and Windows.

The loop is the product. EditSnappy just makes every beat of it fast, safe, and dependable. Watch it on the homepage →

← Back to the inline editing guide · EditSnappy home →