Embiody 0.9 is a Windows browser preview designed for a person and an AI agent to use together. On November 15, Embiody Studio said it had moved the product from closed testing into public beta. The browser runs on the person's computer, while the open-source BrowserDo MCP server gives compatible agents tools to read pages and operate tabs. The headline idea is co-driving: an agent can keep working in the background, then hand a tab to its user for a step such as signing in or paying.
How does Embiody let an agent work while a person uses the computer?
The agent connects through BrowserDo, an MCP server that exposes browser actions such as taking a page snapshot, clicking, typing and reading several pages. Embiody says agent-controlled tabs continue running when they sit behind other tabs or windows, so the browser does not have to stay in front of the person. The company says users can inspect an agent-controlled tab and take it over; when an agent needs a human step, it can hand the same tab to the person and resume after the handoff.
This shared-tab approach is different from sending a URL to a person to finish in another browser. A sign-in, one-time code, file upload or payment can stay in the same browsing session, with the user taking the step that should remain under human control. The BrowserDo repository says the agent also asks before taking over a tab the person is using. These controls describe the product's intended interaction; they do not make every sensitive action safe to delegate.
What does BrowserDo add beyond basic browser clicks?
BrowserDo returns a structured snapshot that numbers the page elements the agent can act on. Its repository says the snapshot omits elements hidden behind overlays, can expose browser prompts, and rejects stale element numbers rather than reusing them after a page changes. A batch tool can combine actions such as clicking, typing and submitting before returning a fresh snapshot. The goal is to give the agent a consistent view of the browser engine and reduce repeated page-reading calls.
Embiody also presents its own comparisons with Chrome and Playwright-based automation: a timer test in a covered window, trials on four sites with bot checks, and page-reading and form-filling examples. Those are the company's demonstrations, not an independent benchmark or evidence that every site will behave the same way. In particular, Embiody's claim that its local browser can pass checks that stop other automation should not be read as permission to evade a site's rules. The end-user agreement says users remain responsible for complying with the terms of the websites they or their agents visit, including restrictions on automated access.
Who can try Embiody 0.9, and what does it cost?
The announcement and BrowserDo documentation limit the current browser to 64-bit Windows 10 or 11. BrowserDo requires Node.js 20 or newer and installs the Embiody browser the first time it starts; the repository says that download is about 140 MB. BrowserDo is an Apache-2.0-licensed MCP server. Embiody's browser is a separate preview product covered by its end-user agreement, which currently grants free use but says the preview may change or stop working. Mac and Linux builds are not available in the announcement.
What should developers know about profile and page data?
By default, BrowserDo operates in Embiody's Default profile, which can contain the user's cookies and sign-ins. Embiody's privacy policy says page content read by BrowserDo goes to the agent program running it; where that program sends the content depends on the connected agent and model provider. A separate `EMBIODY_USER_DATA_DIR` can isolate the agent in another profile. BrowserDo also keeps a local, size-limited log of visited URLs and actions, though its documentation says it does not include page content. Treat the browser session as access to real signed-in accounts, and use a separate profile when that access is not intended.
The company says it does not collect browsing history or page content, but its policy also describes updater requests that report product and version details, install channel and activity counters. Its privacy statement is more specific than a blanket claim that the software sends no data. Developers should read the current policy and the policies of the agent and model they connect before exposing work accounts, customer records or payment pages.
How does Embiody differ from other agent-browser projects?
Embiody is a general-purpose desktop browser that lets a human and agent share browser state. VIBPS has also covered Pomerado, which turns described website workflows into reusable MCP integrations; that project targets repeatable, site-specific operations rather than co-driving one desktop browser. Embiody's approach may suit tasks where a person needs to inspect or resume the exact session, while its Windows-only preview and dependence on the local profile narrow where it fits.
For makers, the release is an example of software built around a person and an agent sharing ongoing activity instead of treating a prompt as the whole product. VIBPS is a social network for software where makers can share what they build and grow an audience around their apps. Embiody is still a preview: its background behavior, handoffs and benchmark claims should be evaluated against a maker's own task, account permissions and the sites involved.