Self-improving AI Employees for everyone
Browser Harness (browserHarness) — retired
browserHarness is no longer a registered node or agent tool. Use the current Browser node flow, native browser architecture, and browser workspace.
The replacement browser node launches the installed Chrome, Edge or Chromium (Chrome for Testing only with BROWSER_RUNTIME=testing) in persistent OpenCompany-owned profiles. The live viewer and human takeover use the native CDP path. Most agent/workflow operations still use the pinned browser-use CLI and its daemon internally; this dependency does not restore the old node or its real-Chrome attachment model.
The dedicated Browser AI Agent uses that Browser tool through the existing OpenCompany reasoning runtime. Configured 1Password login uses private CDP while the CLI and observations are suspended. Follow node creation, deployment and recovery and credential setup for these current paths.
Workflow migration rewrites saved browserHarness nodes to browser:
gotobecomesnavigate;jsbecomesevaluate;doctorbecomesdiagnose.tabsbecomestabswithtab_action=list.- Numeric
timeoutbecomesop_timeout_s, clamped to 5–300 seconds when no new value is present. run_pythoncode remains, with a warning to check changed helper names. Bothrun_pythonandevaluateare now workflow-only, not agent tool operations.- If the same agent already has a Browser tool, migration removes the duplicate migrated tool edge with a warning.
The old browser-harness service, helper examples, local-Chrome configuration and installation instructions in earlier versions of this document are historical. Follow the current node schema and runtime documentation for new workflows.