Release webcmd v0.8.0: Lean, Mean and Modular · agentrhq/webcmd

Highlights

Local self-learning site memory: Browser workflows can now retain verified navigation and workflow knowledge under ~/.webcmd/sites. Learning stays out of normal command output and includes candidate capture and search, conflict-aware checkpointing, optional seed initialization, and bounded memory files.
Selectable local browser runtimes: Keep bundled Cloak as the default, reuse an installed Google Chrome, opt into SLAB on macOS, or select a compatible Chromium executable by absolute path.
One browser skill contract: webcmd skills add and supported plugins now install a single webcmd-browser skill. Adapter, search, fetch, and plugin workflows remain available directly through the CLI.

Improvements

Installed Google Chrome uses an isolated ~/.webcmd/chrome/profiles directory and a Webcmd-owned, nonzero loopback CDP port. Normal headed launches retain Chrome’s native navigator.webdriver value, without claiming general automation undetectability.
Custom Chromium builds receive separate, deterministic profile directories, preventing them from overwriting managed Cloak profiles.
webcmd setup --status now reports the configured browser selection, while webcmd doctor identifies both the selected browser and live runtime.
SLAB setup reuses an existing installation and verifies its code signature and bundle identifier before launch.
Chrome process ownership, cleanup, locked-profile recovery, and CDP endpoint verification have been hardened.
Browser page binding can use either a stable page selector or target ID.
Optional site-memory seeds are fetched only when WEBCMD_GLOBAL_MEMORY_URL is configured and no local memory exists. Set WEBCMD_GLOBAL_MEMORY=off to disable seed lookup.
Candidate evidence can record the public egress IP locally; set WEBCMD_CANDIDATE_PUBLIC_IP=off to disable that lookup. Candidate provenance is not included in ordinary output or pushed by the local site-memory repository.
Added setup guides for Aider and Cline, and refined agent-harness navigation and naming across the documentation.

If you used beta site memory, remove the affected product’s old ~/.webcmd/sites/<product>/sitemap/SITE.md before first use, or remove that product directory if it is no longer needed. Beta memory is not guaranteed to migrate.