Where does Jev come in here? The README never mentions it.

It does not. The README describes a browser agent that runs as an extension and needs your own OpenAI-compatible LLM API key; no Jev endpoint, question type or configuration appears anywhere in it. If typed routing is what you want here, you would be wiring it in yourself.

Can I use this commercially or build a competing browser agent?

Not a competing one. The PolyForm Shield 1.0.0 license lets you modify the code and install it for your own use and redistribute under its terms, but forbids using the software or derivative works to provide a product or service that competes with DomA or its commercial edition, whether free or paid.

Do I have to build it, or is there a prebuilt package?

Either. Releases publishes a prebuilt package you unzip and drag onto the extensions page with Developer mode on, or you clone and run npm install and npm run build, then load dist/desktop/open as an unpacked extension. Building from source needs Node 20+, and running it needs Chrome or Edge.

Is the Chrome and Edge store version the same code?

No. The store builds are a separate commercial edition built on this open-source core, adding video download, a userscripts manager and ad blocking. The repository is the core, and npm run dev is the contributor path rather than an end-user install.

Which browsers and runtimes does DomA need?

Chrome or Edge to run, and Node.js 20+ only if you build from source; a prebuilt package from Releases needs no toolchain, just the browser and your own OpenAI-compatible LLM API key.

Who maintains the DomA browser agent?

It is a browser agent from Stay Browser, released as the open-source edition alongside commercial Chrome and Edge builds; the repository is the core, and the store builds are the commercial edition.

Can I run it from source for development?

Yes. After cloning, npm install then npm run dev is the contributor path, and npm run build produces dist/desktop/open, which you load as an unpacked extension with Developer mode on.

Jev directory

CommunityJev Tools & CLIs

DomA

An open-source browser agent extension for Chrome and Edge that browses, fills forms, clicks, and collects data, letting any extension-capable browser act as an AI browser with your own LLM key.

See highlights Open github.com

Stars: 145
Language: TypeScript
Reading time: 3 min
Published by: Community
Author: dom-actions
Last verified: Sep 2026

dom-actions/doma

Organization repository on GitHub

View on GitHub

The open-source of DomA, an AI automation agent for the browser.

Forks: 22
Last pushed: Updated Oct 2026

Repo stats from the GitHub API, cached Oct 2026.Homepage

About this project

A browser agent from Stay Browser . DomA /ˈdoʊmə/ is an open-source AI web automation agent that runs in the browser. It helps you browse, fill forms, click, collect, and handle other web tasks. With DomA installed, you don't need a dedicated "AI browser" — any extension-capable browser becomes your AI browser. Requirements: Node.js 20+ (for building from source), Chrome or Edge, and your own LLM API key (OpenAI-compatible providers, etc.).

Quoted from the project's README. Read the full README.

Tagscommunity typescript browser chrome-extension agents

Works forJev for Classification

Used inJev for Software & DevTools

Highlights

Runs as an extension, so no dedicated AI browser is needed; the commercial Chrome and Edge builds add video download, userscripts, and ad blocking.
Build from source with npm install and npm run build, then load dist/desktop/open as an unpacked extension with Developer mode on.
Requires Node.js 20+ for building and your own OpenAI-compatible LLM API key; a prebuilt package is also published on Releases.
Licensed under PolyForm Shield 1.0.0, which forbids using it or derivatives to provide a competing product or service.

Quickstart

bash

git clone https://github.com/dom-actions/doma
cd doma && npm install
npm run build

Watch out

PolyForm Shield License 1.0.0: you may modify and redistribute, but not build a competing product or service. Needs Chrome or Edge, Node.js 20+ for source builds, and your own LLM API key.

Questions about this entry

Short answers drawn from the linked project or page.

Reactions & coverage

Posts, threads, and videos about this entry from around the web.

X: Agentic browsing in Chrome

X: Text-to-screenshot (Malay Vasa)

X: Google's MediaPipe Decision Maker, tested in the browser

X: Playwright CLI + Jev vs Playwright MCP

From the Jev guides

Original write-ups on what this entry is for.

Browser Agents and Computer Use: What to Copy from the First Breakout Category

Sep 22, 2026

Browser loops are long series of small decisions, and the expensive model does not need to make any of them. The patterns behind the fastest agents, from element tables to OCR plus accessibility trees.

Jev Tools & CLIs#browser#computer-use#agents

Read article

Jev at home: voice pipelines, Assist routing, and sentinels

Oct 16, 2026

How Home Assistant conversation agents, macOS voice pipelines, and an advisory sentinel put a fast typed decision in the loop — one call per utterance, thresholds in code, and a daily token budget.

Jev Tools & CLIs#home-assistant#voice#automation

Read article

Search visibility, audited by decisions

Oct 16, 2026

Jev-based SEO tools split the crawl from the call: deterministic crawlers count and parse, while typed judgments rank fixes, place internal links, score search results, and track AI-answer mentions — with costs and caveats attached.

Jev Tools & CLIs#seo#search-visibility#audits

Read article

From the Jev AI model community

Posts from builders shipping with Jev right now.

Follow @typesafeai

DomA

About this project

Highlights

Quickstart

Questions about this entry

Where does Jev come in here? The README never mentions it.

Can I use this commercially or build a competing browser agent?

Do I have to build it, or is there a prebuilt package?

Is the Chrome and Edge store version the same code?

Which browsers and runtimes does DomA need?

Who maintains the DomA browser agent?

Can I run it from source for development?

Reactions & coverage

More Jev resources like this

From the Jev guides

From the Jev AI model community