Mercury CLI

Notes

Mercury CLI 1.0.0 is here

· by @dubsthedev · 1.0.0

Today, seven months from writing the first line of Mercury, I'm putting out Mercury CLI 1.0.0. This is the full release. The betas and release candidates are behind us. I now use Mercury for all of my own work, including building Mercury itself.

What you can do with 1.0.0

The Computer tool reads a screen as a short numbered outline and acts by row number. So a desktop task that used to take dozens of Mercury calls now takes a handful. Every result's second line says what is on the screen after the act.

Every model now reads documents. A PDF opens as numbered text with page markers. Office files keep their headings, lists, tables, notes and formulas. Scanned pages and images read through the system's OCR (macOS Vision, Windows OCR, or an installed Tesseract), with Arabic among the languages read.

The Document tool creates DOCX, PDF, PPTX, XLSX, HTML and Markdown from Markdown or structured content. It converts between them, merges and splits PDFs, and writes bibliographies with DOI lookup. Every write goes through the usual permission check.

Local image generation grows in this release: SDXL and Pixel Party XL run once you set them up with /imagesetup. You can give reference images with a denoising strength and optional masks on every image model. You can use your own checkpoint files and LoRAs. ControlNet (canny, depth, pose) works with batches, sheets and pixel-art palettes. Local images and video also run on x64 Windows and Linux now.

Opening up

Mercury now serves its own tools to other agents over MCP. Run mercury mcp-server and another agent can hand Mercury work and read what it did.

With mercury tune, you can export your own sessions as a scrubbed training book, have a model write the reasoning for each turn, train an adapter on a rented GPU with a money pause that never terminates the machine, and install the result locally.

Smaller changes

A project's MCP servers start only once you approve them.

The update notice is yellow and stays until you update, so you don't miss a support update.

Four new debug adapters join the set: Flutter, CodeLLDB for Rust, PHP with Xdebug, Bash.

/copy puts the last reply on the clipboard whole, with its line breaks, emoji and right-to-left text.

A repository's own git helpers never run inside Mercury's git commands.

An unattended run sends less with each request and makes fewer requests, with every capability, thinking budget and output limit kept.

This release also fixes issues with small local models, headless runs, crewmates, /compact, and /imagesetup and /localsetup on Windows.

Installing Mercury 1.0.0

If you're installing Mercury for the first time, you have three ways in: the one-line installer on mercury-cli.ai, Homebrew (the whq02/mercury tap), or npm (mercury-tech-cli). They all install the same Mercury.

If you're on a release candidate, install 1.0.0 once by any of those three. After that, mercury update keeps it current.

What's next

I'll keep working on local models and paving the training road. And as always, I'll build the things Mercury's users ask for. More on all of that as it happens. For now, enjoy 1.0.0. I'll be here if you need anything.