Repository navigation
v0.1.1
v0.1.1 — pinned ceremony browser start
One hardening fix on top of v0.1.0.
Fixed
sessions.ensurenow starts the managed browser pinned to theopenclawprofile in headless mode (openclaw browser --browser-profile openclaw start --headless) instead of inheriting config defaults. After a Gateway restart, a zero-config node browser proxy auto-routed the default profile to a remote node (a Mac), launching Chrome there while ensure polled the local CDP endpoint and failed withBROWSER_UNAVAILABLE. The pinned command keeps the start local regardless of config-side defaults; thecdpReachablegate remains the source of truth for readiness. Gateway-side routing config is orthogonal and untouched.
Tests
- 83/83 passing (81 + 2 new: the default start spawns the pinned command; no spawn when CDP is already reachable).
Engineering status
- Same known blockers as v0.1.0: the CI release gate fails at
toolfactory validateon pinned toolfactory@0.2.1 scaffold drift (self-inconsistentopenclawVersion), so these assets are built and attached from the verified local tree; npm registry publication awaits anNPM_TOKENsecret / trusted publisher on the repo.