Mercury CLI
Terminal environment for running parallel AI coding agents that edit files and run tests.
Tested on Linux
Use it
Linux x86_64
You need first
- System packages:
git
npm global install of mercury-tech-cli shim
npm install -g mercury-tech-cliforced first-run payload install plus version check
MERCURY_INSTALL_ARGS=--force mercury --version
Where the README and reality differ
- README: npm install -g mercury-tech-cli then check mercury --version
What worked: Prefix the first run with MERCURY_INSTALL_ARGS=--force (i.e. MERCURY_INSTALL_ARGS=--force mercury --version) so the product installer overwrites the npm shim at ~/.local/bin/mercury; without it the installer refuses ('stable command NOT written: an existing non-Mercury-managed command is already at…
Check that it works
mercury --version 2>&1The output should contain “Mercury 1.0.1”.
Run mercury --version to confirm the install, then run mercury to start.
What it does
These come from the README; pickfit didn’t check them one by one.
- Run several AI coding sessions at onceNot tested
- Use both provider and local modelsNot tested
- Start agents and workflows across companiesNot tested
- Step through tests and debuggersNot tested
How far pickfit got
Linux x86_64
- Installs
- Starts
- Main function works
- Works offline
macOS and Windows: the project says it runs there; pickfit hasn’t tried it.
Good for
- read and edit files and run shell commands via agent
- run parallel coding sessions
- run one-shot prompts headlessly
How pickfit tested it
Each run starts from a clean machine and follows the steps above. How pickfit verifies
Linux x86_64
Its main function works
- Replayed from scratch
- Works offline
- Checked on 30 Oct 2026
- Version 1.0.1
Differences the test machine hit
- README: check mercury --version after opening a new terminal
In the test: First invocation of mercury downloads the ~27MB linux-x64 release archive (v1.0.1), verifies checksum, and stages ~/.mercury/versions/1.0.1 before printing the version; allow ~20s. Direct versioned launcher ~/.mercury/versions/1.0.1/mercury --version answers instantly. - README: run `mercury` inside a repository; headless via mercury run
In the test: Interactive `mercury` needs a TTY/repository and `mercury run "<prompt>"` needs a signed-in model provider, so neither was runnable with no API keys; verified function with `mercury --help` and `mercury update --check` (no sign-in needed) instead.