For AI agents: the index of this site is https://dejo.run/llms.txt, and every page is also served as markdown (add .md to its address, or send Accept: text/markdown).

dejo

Dejo vs browser-use

The short answer: browser-use is a browser agent. You give it a task and its own model does the work in a real browser. Dejo is a browser tool with no model: it works under the agent you already use (Claude Code, Codex, Cursor), and it remembers each website task, so every run after the first is one tool call with zero model calls. If you want an agent that runs on its own in a Python script, pick browser-use. If you already have an agent and it keeps redoing the same website work, pick Dejo.

Side by side

Dejobrowser-use
what it isMCP server for your agentbrowser agent (Python library) with an MCP server
who does the thinkingyour agent (Claude Code, Codex, Cursor...)browser-use's own agent loop, on the model you give it
needs a model API keynoyes, "runs on any LLM", or Browser Use Cloud
remembers a task between runsyes, replays with zero model callssaves run history; its replay still calls a model for extract steps and the summary
checks that each step landedyes, every saved stepno per-step check on replay
when a site changesstops at the one step that moved; your agent fixes that stepthe model works it out again
MCP tools5 (dejo_run, dejo_login, dejo_profile, dejo_memory, dejo_manage)16 with browser-use --mcp, 2 with --cli-mcp
captchas and bot blocksstops and hands over to you, by designBrowser Use Cloud offers stealth browsers
languagePython 3.11+Python
licenseMITMIT
tokens, our real-site benchmark251K first run, 89K afternot measured yet

The browser-use column comes from its own README and source code, read 13 November 2026. Every row, with a link to the line of code it comes from, is in Dejo's capability list. browser-use has not been through our benchmark yet, so there is no token number for it here.

Agent or tool: the real difference

browser-use describes itself as "the open-source browser agent". You hand it a task in plain words and a model drives the browser until the task is done. Its README says the model now works "by writing Python" in a persistent session, with raw Chrome DevTools access. That is a whole agent: planning, retries, a judge, a loop check, a fallback model. You choose and pay for the model.

Dejo does none of that thinking. Your agent already plans and reasons, so Dejo gives it the browser and the memory:

  1. The first run, your agent explores the site through dejo_run, and Dejo saves each step with a check that proves it worked: the page changed, the file arrived, the field holds the value.
  2. Every run after, dejo_run walks those steps in plain code. No page reading, no model call inside Dejo.
  3. When the site changes, only the step that moved fails, and your agent fixes that one step.

So the cost question is different. With browser-use, every run is a model run. With Dejo, a task your agent has learned costs about one tool call. On our benchmark of 19 tasks on 11 real websites, Dejo's runs after the first averaged 89K tokens against 409K for Playwright MCP, and 17 of the 19 tasks replayed in a single call.

When browser-use is the better choice

When Dejo is the better choice

Set up Dejo

pip install dejo-mcp
playwright install chromium
claude mcp add --scope user dejo -- dejo-mcp

Then ask your agent for something on a website, in your own words. Other agents: Codex, Cursor.

More comparisons: Dejo vs Stagehand, Playwright MCP alternative and the best browser MCP for Claude Code.

FAQ

What is the difference between browser-use and Dejo?

browser-use is a browser agent: you give it a task and its own model does the work. Dejo has no model. It is a browser tool for the agent you already use, such as Claude Code, Codex or Cursor, and it remembers each task so the next run is one tool call with zero model calls.

Does browser-use need an API key?

It needs a model to drive it. Its README says it runs on any LLM, so you bring the model and its key, or use Browser Use Cloud. Dejo needs no key of its own: your agent does the thinking.

Can browser-use replay a task without a model?

Partly. It can save a run's history and run it again, but per its source the replay still calls a model for extract steps and the summary, and it has no check that each step landed. Dejo replays a learned task with zero model calls and checks every step.

Can I use browser-use and Dejo together?

Yes. browser-use has its own MCP server (browser-use --mcp) and Dejo is a separate MCP server, so an agent can have both. Use browser-use when you want its agent to take a task on its own, and Dejo for website tasks you repeat.