Skip to content

OpenChrome MCP v1.13.0

Choose a tag to compare

@shaun0927 shaun0927 released this 07 Sep 16:53
· 3093 commits to 3f6fd67f3e2ed245ba30374ec1e55b689391f79c since this release

OpenChrome 1.13.0 adds explicit browser input control and improves account-state continuity and cancellation reliability.

  • Observe active/recent operations and pause, drain, verify and explicitly resume a managed tab with oc_browser_control.
  • Restore saved state independently per browser context without replacing fresh live cookies/local storage.
  • Preserve active tabs at capacity; bound target, screenshot and operation admission. Preserve human-held tabs during idle/pressure cleanup.
  • Handle MCP cancellation per client session, apply deadlines to recovery, and avoid replaying writes with uncertain outcomes.
  • Keep explicit headless policy and lazy owned-browser startup; limit startup blank-tab cleanup to the owned target.
  • Read tab metadata in bounded parallel batches and fix early return in same-line JavaScript statements.

Validation and limitations

The implementation passed 190 focused tests, Windows/Linux installed real-Chrome CI, controlled four-account isolation and upgrade/restart fixtures. Mixed latency measurements do not establish a consistent speedup. External-site SSO/MFA, long-running memory stability and every host configuration are not certified by the fixtures. Human drain covers tracked handlers/CDP commands, not website background activity.

Usage: https://github.com/shaun0927/openchrome/blob/v1.13.0/docs/agent/browser-control.md
Detailed implementation evidence: #1664

The attached tarball is the tested package. npm registry publication status is recorded separately; the existence of this GitHub release does not imply npm publication.

Release verification at main 3f6fd67f3e2ed245ba30374ec1e55b689391f79c:

npm registry publication is pending: the release operator is not authenticated (npm whoami: ENEEDAUTH). Until publication, download and install the attached tarball; npm install openchrome-mcp@latest still resolves to the previous registry release.