I open-sourced DomA: an AI automation agent for the browser

Most “AI browser” products ask you to abandon the browser you already live in.

New Chromium fork. New profile. Friction with passwords, extensions, and muscle memory. Your logged-in sessions don’t come along for the ride. DomA takes the opposite bet: stay in Chrome (or Edge), keep the tab you’re already on, and run an agent from a side panel.

Browser agents often look impressive in demos and fall apart on real sites:

DomA’s open core is built around two answers to that pain: Jev inner loops and solidified Skills.

DomA is a Chrome/Edge extension, not a standalone AI browser and not a hosted “cloud browser.” You keep:

The open edition is Bring Your Own Key: OpenAI-compatible providers (and similar endpoints). You’re not locked into our model marketplace. Keys stay in your setup; model calls go to your chosen provider. (That’s important for developers — but the product thesis is still “agent in your browser,” not “BYOK for its own sake.”)

Interactive elements get numbered overlays. The model sees a screenshot with markers and chooses index-based actions instead of guessing fragile CSS selectors.

Synthetic events for speed, CDP fallbacks for stubborn widgets, and coordinate-level interaction when needed.

Large tool payloads can be spilled out of the chat transcript and re-read via refs — so long tasks don’t drown the model in noise.

screenshot → main LLM → click → screenshot → main LLM → type → … That burns latency and invites inconsistency between steps.

Jev is DomA’s optional inner loop on browser_screenshot (act/verify):

Even with good grounding, accuracy compounds only if successful procedures become reusable. DomA supports Agent Skills:

There is also a commercial store build with extras (video download, userscripts, ad blocking, …). This post is about the open core.