Release webcmd: v0.8.1 · agentrhq/webcmd

Highlights

Local Chrome setup can now import cookies from installed Chrome profiles, allowing Webcmd to start with existing sign-ins. Setup maps Chrome’s default profile to Webcmd’s default profile and creates stable names for additional profiles.
Use --chrome-profile to import one Chrome profile, or --import-chrome-cookies and --no-import-chrome-cookies to control cookie import in non-interactive setup.

Redesigned webcmd --help with an ASCII banner, clearer command groups, global options, examples, agent guidance, and dynamic site/external CLI lists. Structured JSON and YAML help remain unchanged.
Browser readiness messages now identify the configured runtime and provide relevant guidance for SLAB, Cloak, Chrome, and custom runtimes.

Improved SLAB session orchestration:
- Native profile IDs such as Profile 1 are now supported.
- session list exposes unbound SLAB windows as temporary discovered sessions.
- browser tabs discovers pages without focusing or claiming them.
- browser bind --page <page-id> claims the page’s complete window, including sibling tabs.
- Closing an adopted human session detaches Webcmd while leaving the window open.
- browser close --page <page-id> can close an exact tab; --force permits closing adopted human tabs.
- Explicit session closure now cleans up SLAB session records correctly.
- The initial blank page is claimed instead of leaving an unowned tab behind.
Fixed installed Chrome on macOS unloading its profile or terminating after the last visible probe window closes.
Browser daemon startup no longer inherits caller-owned temporary-directory environment variables, improving reliability when launched from short-lived environments.