Press one key — Keyfloe reads the email currently in focus, drafts a contextual reply in your voice, and pastes it back at the cursor. Works across Mail.app, Spark, Superhuman, Gmail web, and Outlook web.
Email Reply, in one keystroke
You read the email. Switch apps. Paste it into a chat tool. Ask for a reply. Paste back. Send.
Email tab, ChatGPT tab, back to email — half a dozen window flips per reply.
You have to summarise the thread or paste it in, every time.
Generic AI replies don’t sound like you. Formality drift everywhere.
Copy-paste accidents send the wrong reply to the wrong thread.
One key. The draft is in your reply field.
macOS accessibility APIs grab what you’re looking at — no copy-paste.
Tone presets per binding. fn-tap for casual, Right-Option-tap for formal.
Keyfloe drafts; you edit and hit send. Nothing leaves on its own.
Mail.app, Spark, Superhuman, Gmail web, Outlook web — same key.
Keyfloe uses macOS accessibility APIs to read the visible content of the focused window. For native clients (Mail.app, Spark, Superhuman) that means the thread you’re viewing. For webmail (Gmail, Outlook) it reads the visible message in the browser.
Email Reply only fires when an email client is the focused app. If you’re elsewhere, the key binding does nothing — pressing the same key again with the email client focused will work.
Yes. Keyfloe pastes the draft into the reply field — you can edit it, reorder it, or rewrite parts before hitting send. Nothing is sent on your behalf.
Tone is per-binding. You can bind Email Reply to multiple keys with different tone presets — e.g. fn-tap for casual, fn-hold for formal, Right-Option-tap for brief.
Yes — over time, Keyfloe samples your previous outgoing emails (with permission) to bias the draft toward your voice. Disable this in Settings if you’d rather not.
Keyfloe reads the visible thread and drafts a reply addressed to the original sender. You can edit recipients before sending — Keyfloe doesn’t change the To/Cc fields on its own.