Work / Magically — AI inside the editor

Magically — AI inside the editor

A Chrome extension that embedded streaming AI writing assistance and voice input inside Gmail, Outlook, and X.com.

Problem

Writing assistance was useful inside the editor where the user was already working.

Constraints

Gmail, Outlook and X.com have different DOM structures, focus behavior and editor semantics.

What I did

Magically was a Chrome extension that put AI writing help right where people already wrote: Gmail, Outlook, and X.com.

The product constraint

I didn't want to build another destination. Users were already inside an editor. The assistant had to show up in that context, stream suggestions into the writing flow, take voice input for drafting, and get out of the way when it wasn't needed.

The engineering constraint

Every host page had its own DOM, editor semantics, focus behavior, and mutation patterns. The extension injected an inline assistant without assuming Gmail, Outlook, and X.com exposed equivalent editor APIs. React and TypeScript powered the UI. Server-sent events streamed the model output so it didn't feel like a modal request. Supabase handled the backend.

The lesson was about integration boundaries. AI gets more useful when it's embedded in the workflow that already holds the user's intent, instead of asking them to take that work somewhere else.

Result

A Chrome extension with inline streaming writing assistance and voice input.

Tradeoffs

Embedding inside third-party interfaces avoids an extra destination but requires handling their differing editor behavior.

Stack

ReactTypeScriptSupabaseSSE

Explore more problems I've solved

Bhavin Kamani

A small command line for a curious visitor.