Mercury CLI
Browsing, faster turns, and workspace safety floors
I spent this cycle on the parts of Mercury I use every day: browsing, turn speed, file tools, and keeping the workspace safe. The Browser tool now keeps a persistent Chrome profile per origin so logins and cookies carry across sessions, moves and types at a human pace, and reports on back when a page came from the browser's cache. WebFetch reads GitHub repositories, issues and pull requests, npm, PyPI, crates.io, arXiv and Stack Overflow through their public keyless APIs before falling back to HTML, and /browse opens the file tree from the composer even in /zen or narrow terminals where the side rail is hidden.
On the execution side, read-only tool calls now start running as soon as their block settles in the streaming reply, edits to different files run in parallel, repeated identical tool results collapse to a one-line pointer, and output token caps fit the remaining context window before each request. Read opens zip and tar archives, SQLite databases and office documents directly and supports negative tail offsets, line ranges, tree-sitter outlines and image crop boxes, while Write and Edit update zip entries and keyed SQLite rows and check JSON, YAML and TOML syntax when no language server covers the file. Five safety floors also land to protect credential stores, Mercury's stored credentials, cloud-metadata addresses, the running binary and project instruction and .env files, alongside fixes for /zen crewmate views, popup scrolling at small terminal sizes, compaction view re-anchoring, Windows shell resolution, and PowerShell piped prompts. The full list of changes and fixes is in the 1.0.0-beta.38 release notes.