This release is a pre-release and may not be stable for production use.
meridian-cli
Let coding harnesses call each other. meridian-cli lets agents running in Claude Code, Codex CLI, and OpenCode spawn named specialist agents in the other harnesses, each with the model, cost, and tool environment you configured.
It is for people who already use more than one AI coding CLI and want one team of agents instead of separate chat sessions.
Early development. meridian-cli is not stable. Expect breaking changes in any release. If you need a stable workflow, this project is not ready for you yet.
Why
Good agentic coding is an allocation problem. Some tasks need the strongest model you have; some need cheap, parallel throughput; some need a specific harness feature such as sandboxing, tool behavior, context handling, or integrations.
Without meridian-cli, those choices are trapped inside separate CLIs. Switching harnesses means manually copying context between sessions and hoping the next agent understands what happened.
meridian-cli turns that handoff into a command. A caller can delegate to a named specialist, pass only the context that agent needs, and pick up the result from disk. Use the expensive model where judgment matters, use cheaper agents where throughput matters, and keep every agent inside the harness that fits the job.
One Harness Can Call Another
Demo placeholder: add a short terminal recording or screenshot here showing one coding harness spawning an agent in another harness, then collecting the result with
meridian spawn waitormeridian spawn show.
Install
uv tool install meridian-cli
The package is meridian-cli; the command it installs is meridian.
Other methods
pipx install meridian-cli
pip install meridian-cli
From source:
git clone https://github.com/haowjy/meridian-cli.git
cd meridian-cli
uv tool install --force . --no-cache --reinstall
You need at least one harness installed: Claude Code, Codex CLI, or OpenCode.
Set Up a Project
meridian init by itself only bootstraps meridian-cli project config:
meridian init
To initialize Mars package content in the same step, use setup flags:
meridian init --add haowjy/meridian-dev-workflow --link .claude
For first-run onboarding, bootstrap can do setup + launch in one command:
meridian bootstrap --add haowjy/meridian-dev-workflow --link .claude
--add / --link setup flags cannot be combined with --dry-run.
Usage
Launch an interactive session:
meridian
Or spawn agents directly:
# Code on Codex, review on Claude
meridian spawn -a coder -p "Add rate limiting to the API endpoints"
meridian spawn -a reviewer --from p1 -p "Review the rate limiting implementation"
# Check on work
meridian spawn list
meridian spawn show p1
Agents route to their configured model and harness automatically. Each spawn gets a fresh context window with only the context it needs.
Architecture
graph TB
User([You]) --> Primary["meridian<br/>(primary session)"]
subgraph Packages
Sources["git sources"] -->|"mars add/sync"| Store[".mars/"]
Store -->|"materialize targets"| Tool[".claude/ · .cursor/ · .codex/ · .opencode/ · .pi/"]
end
subgraph Runtime
Primary -->|"meridian spawn"| Router{"Model router"}
Router --> Claude["Claude Code"]
Router --> Codex["Codex CLI"]
Router --> OpenCode["OpenCode"]
end
subgraph State[".meridian/"]
Spawns["spawns + reports"]
Sessions["sessions"]
Work["work items"]
end
Agents --> Primary
Primary --> State
Claude & Codex & OpenCode -->|"meridian CLI"| State
Agent Packages
meridian-dev-workflow — A dev team: architects, coders, reviewers, testers, researchers, documenters, and the orchestrators that coordinate them.
meridian-base — Core coordination primitives. Included as a dependency of meridian-dev-workflow.
Docs
- Getting Started — prerequisites, harness setup, tool integration
- Commands — full CLI reference
- Configuration — config keys, state layout, environment variables
- MCP Tools — tool surface and payload examples
- Troubleshooting — common issues and diagnostics
- INSTALL.md — agent-friendly install guide
Development
uv sync --extra dev
uv run ruff check .
uv run pytest-llm
uv run --extra dev python -m pyright
See DEVELOPMENT.md for full dev setup.
Contributing
This project is not accepting external contributions at this time. The maintainer is keeping it closed to outside contributions until the codebase is stable enough to support them well. Bug reports and feedback are welcome as GitHub issues.
License
1 maintainer
Release files for meridian-cli 0.4.6rc1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| meridian_cli-0.4.6rc1.tar.gz | 984.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| meridian_cli-0.4.6rc1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.3 MB
Release files / meridian_cli-0.4.6rc1.tar.gz
| Download URL | meridian_cli-0.4.6rc1.tar.gz |
|---|---|
| Size | 984.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b0cc81e4800ab78e60fed6d4d00aee2b889adf759d7cc9e7c7491287144612ed
|
|
BLAKE2b-256 checksum How to use checksums |
783227e93283f12911fb3201388d9ca6408fd77c9f5c2ac309dd55fc8ba084b6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 16, 2026.
Transparency logRelease files / meridian_cli-0.4.6rc1-py3-none-any.whl
| Download URL | meridian_cli-0.4.6rc1-py3-none-any.whl |
|---|---|
| Size | 1.3 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7635cebc5bb352be53d9a5ebca355ad47a42534ae1ed6c6f25e076baf2db2847
|
|
BLAKE2b-256 checksum How to use checksums |
b27080b75d8cde4c06e5c4e6bbbace282bdd23a9858c2655b245620f46884104
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 16, 2026.
Transparency log
