Skip to content

Self-improving AI Employees for everyone

2.5 KB
Raw Blame

Browser Harness — historical integration

The separate browserHarness node and its external-Chrome integration have been retired. The supported node and agent tool are both named browser.

Current documentation:

The current runtime launches installed Chrome/Edge/Chromium in a dedicated OpenCompany profile headless inside the workspace UI by default; it neither attaches to nor copies an already running, logged-in personal profile. Chrome for Testing is available only through explicit BROWSER_RUNTIME=testing; a separate desktop window requires BROWSER_HEADLESS=false. Ordinary agent/workflow operations use generated scripts through the isolated, pinned browser-use CLI and its persistent daemon; WebMCP and live viewer capture/control have native CDP paths. Configured 1Password form filling uses that existing private CDP connection only after the CLI daemon and observations are suspended. The presence of browser-harness machinery inside that dependency is separate from the retired OpenCompany node.

The dedicated browser_agent is an OpenCompany SpecializedAgentBase agent, using the existing AI reasoning runtime and Browser tool. It does not adopt the dependency's separate autonomous agent loop. Direct Workspace tasks, durable ownership and protected-login setup are described in Browser workspace, deployment and 1Password credentials.

Saved-workflow migration renames browserHarness to browser and maps goto to navigate, js to evaluate, doctor to diagnose, and tabs to tab listing. Existing Python code is retained with a helper-compatibility warning. evaluate and run_python are now workflow-only; duplicate Browser tool edges created by migration are removed with a warning. See the node flow for complete parameter compatibility behavior.

Do not use the old service paths, installation commands, remote-debugging setup or Python helper examples from this document's history as current setup instructions. Testing-browser and CLI dependency pins are maintained in server/config/browser_runtime.json.