Agent Zero: The Workcell Is Becoming A Visible Computer

What Changed

Agent Zero's commit stream is intensely concrete: native browser, persistent Chromium runtime, browser viewer, tabs, screenshots, annotation, desktop canvas, Office/LibreOffice runtime, file browser, ZIP downloads, Linux desktop controls, OAuth disconnect, quota visibility, and Time Travel workspace history.

The diff-reviewed native browser commit replaces a browser-use agent with a direct Playwright-powered browser tool, live WebUI viewer, session controls, status APIs, configuration, and extension management. It also moves the legacy browser-use approach out of core.

Operator Consequence

The frontier is leaving the chat box. For many workflows, the useful surface is a visible computer: browser, file system, desktop, documents, screenshots, canvas, and recoverable state.

This makes agent work easier to trust because the user can see more of what the agent is doing. It also creates new authority questions around browser sessions, document runtimes, OAuth, file access, and desktop controls.

Bitter Consequence

Agent Zero is the clearest source for BitterGrid's workcell doctrine in this window. A workcell should not be an invisible shell. It should be a bounded, inspectable environment where browser, files, runtime, screenshots, credentials, and artifacts can be attached to receipts.

Bitter should test Agent Zero as an agent engine and as a product lesson.