meridian-cli 0.0.25__tar.gz

meridian_cli-0.0.25/.gitignore

@@ -0,0 +1,20 @@
+__pycache__/
+*.pyc
+*.pyo
+.venv/
+*.egg-info/
+dist/
+build/
+.pytest_cache/
+.ruff_cache/
+
+scratch/
+tmp/
+
+.orchestrate/
+.scratch/
+.codex/config.toml
+
+err
+out
+.mars/

meridian_cli-0.0.25/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Jimmy Yao
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

meridian_cli-0.0.25/PKG-INFO

@@ -0,0 +1,367 @@
+Metadata-Version: 2.4
+Name: meridian-cli
+Version: 0.0.25
+Summary: Orchestrate CLI + MCP server for multi-model agent workflows
+Project-URL: Homepage, https://github.com/meridian-flow/meridian-cli
+Project-URL: Repository, https://github.com/meridian-flow/meridian-cli
+Project-URL: Issues, https://github.com/meridian-flow/meridian-cli/issues
+License: MIT
+License-File: LICENSE
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Software Development :: Libraries
+Classifier: Topic :: Utilities
+Requires-Python: >=3.12
+Requires-Dist: aiohttp>=3.11
+Requires-Dist: coolname>=4.0.0
+Requires-Dist: cyclopts>=3.0
+Requires-Dist: mars-agents==0.0.13
+Requires-Dist: mcp>=1.0
+Requires-Dist: pydantic-settings>=2.13
+Requires-Dist: pydantic>=2.12
+Requires-Dist: python-frontmatter>=1.1
+Requires-Dist: structlog>=25.0
+Provides-Extra: app
+Requires-Dist: ag-ui-protocol>=0.1; extra == 'app'
+Requires-Dist: fastapi>=0.115; extra == 'app'
+Requires-Dist: uvicorn[standard]>=0.34; extra == 'app'
+Requires-Dist: websockets>=14.0; extra == 'app'
+Provides-Extra: dev
+Requires-Dist: pyright>=1.1.400; extra == 'dev'
+Requires-Dist: pytest-asyncio>=0.24.0; extra == 'dev'
+Requires-Dist: pytest>=8.4.0; extra == 'dev'
+Requires-Dist: ruff>=0.12.0; extra == 'dev'
+Provides-Extra: templates
+Requires-Dist: jinja2>=3.1; extra == 'templates'
+Description-Content-Type: text/markdown
+
+# meridian
+
+[PyPI](https://pypi.org/project/meridian-cli/)
+[Python](https://pypi.org/project/meridian-cli/)
+[License](LICENSE)
+[CI](https://github.com/meridian-flow/meridian-cli/actions)
+
+> **Alpha** — API may change between releases.
+
+A coordination layer for AI agents. One agent spawns others, routes them to the
+right model, and reads their results — across Claude, Codex, and OpenCode.
+
+You talk to one agent. It delegates the rest.
+
+## What This Looks Like
+
+You say: *"Refactor the auth module to use JWT tokens."*
+
+The orchestrator agent — running inside Claude, Codex, or any supported
+harness — autonomously runs commands like these:
+
+```bash
+# Spawn a researcher on a fast model to explore the codebase
+meridian spawn -a researcher -p "Map the auth module — token handling, session management, middleware"
+# → {"spawn_id": "p1", "status": "running", "model": "gpt-5.3-codex"}
+
+# Wait for it, then read what it found
+meridian spawn wait p1
+meridian spawn show p1
+
+# Spawn coders in parallel on Codex, passing the researcher's findings
+meridian spawn -a coder --from p1 -p "Phase 1: Replace session tokens with JWT" -f src/auth/tokens.py
+# → {"spawn_id": "p2", "model": "gpt-5.3-codex"}
+meridian spawn -a coder --from p1 -p "Phase 2: Update middleware validation" -f src/auth/middleware.py
+# → {"spawn_id": "p3", "model": "gpt-5.3-codex"}
+meridian spawn wait p2 p3
+
+# Fan out reviewers with different focus areas
+meridian spawn -a reviewer --from p2 -p "Review phase 1 — focus on token expiry edge cases"
+# → {"spawn_id": "p4", "model": "gpt-5.4"}
+meridian spawn show p4
+
+# Pick up context from a prior session
+meridian session search "auth refactor"
+meridian report search "JWT decision"
+```
+
+Every spawn writes logs, reports, and metadata to shared state under `.meridian/`.
+The orchestrator reads those reports, decides what to do next, and keeps going.
+If the session gets compacted or resumed later, the state is still there.
+
+**The human doesn't run these commands.** The agent does — meridian is the CLI
+that agents use to coordinate other agents.
+
+## Agent Packages
+
+**[meridian-dev-workflow](https://github.com/meridian-flow/meridian-dev-workflow)** — A full dev team: architects, coders, reviewers, testers, researchers, documenters, and the orchestrators that coordinate them. Includes skills for design methodology, implementation planning, code review, and structural hygiene. This is what most users want.
+
+**[meridian-base](https://github.com/meridian-flow/meridian-base)** — Core coordination primitives: the base orchestrator, subagent, and skills for spawning, state tracking, and session context. Included as a dependency of meridian-dev-workflow.
+
+Packages are managed by **[mars](https://github.com/meridian-flow/mars-agents)**, an agent package manager that installs agent profiles and skills from git sources into your project's `.agents/` directory.
+
+## Install
+
+```bash
+uv tool install meridian-cli
+```
+
+Verify:
+
+```bash
+meridian --version
+meridian doctor
+```
+
+Alternative install methods
+
+```bash
+pipx install meridian-cli    # if you prefer pipx
+pip install meridian-cli     # into a Python environment
+```
+
+From source:
+
+```bash
+git clone https://github.com/meridian-flow/meridian-cli.git
+cd meridian-cli
+uv tool install --force . --no-cache --reinstall
+```
+
+Development environment (no tool install):
+
+```bash
+uv sync --extra dev
+uv run meridian --help
+```
+
+If `meridian` is not on your PATH: `uv tool update-shell`
+
+
+
+## Set Up a Project
+
+```bash
+cd your-project
+meridian init --link .claude
+meridian mars add meridian-flow/meridian-dev-workflow
+```
+
+This initializes `.meridian/`, links `.agents/` into `.claude/` so Claude Code
+discovers your agents and skills, and installs the full dev team (coder,
+reviewers, testers, architect, etc.) plus core coordination primitives.
+
+For just the core primitives:
+
+```bash
+meridian mars add meridian-flow/meridian-base
+```
+
+To link into other tool directories (e.g. Cursor):
+
+```bash
+meridian mars link .cursor
+```
+
+### Prerequisites
+
+**Platforms:** macOS and Linux. Windows is supported via
+[WSL](https://learn.microsoft.com/en-us/windows/wsl/) (native Windows is not
+supported).
+
+You need at least one harness CLI installed and authenticated:
+
+
+| Harness     | Model prefixes                  | Install                                                              |
+| ----------- | ------------------------------- | -------------------------------------------------------------------- |
+| Claude Code | `claude-`*, `sonnet*`, `opus*`  | [docs.anthropic.com](https://docs.anthropic.com/en/docs/claude-code) |
+| Codex CLI   | `gpt-*`, `codex*`, `o3*`, `o4*` | [github.com/openai/codex](https://github.com/openai/codex)           |
+| OpenCode    | anything else                   | [opencode.ai](https://opencode.ai)                                   |
+
+
+Claude and Codex are the most exercised paths today. OpenCode has adapter
+support but lighter day-to-day coverage.
+
+**Primary session:** Only Claude Code supports system prompt injection
+(`--append-system-prompt`), which is how Meridian loads agent skills into the
+primary session. Codex and OpenCode work well as **spawn targets** but aren't
+as suited as the primary harness.
+
+### Tool integration (Claude Code, Cursor, etc.)
+
+If you didn't pass `--link .claude` during `meridian init`, you can link later:
+
+```bash
+meridian mars link .claude
+```
+
+This symlinks `.agents/` into `.claude/` so Claude Code auto-discovers your
+installed agents and skills. Without linking, `meridian spawn` still works
+(it injects context directly), but interactive sessions won't auto-discover
+agents and skills.
+
+To unlink: `meridian mars link --unlink .claude`
+
+## Quick Start
+
+```bash
+meridian                  # Launch a primary agent session
+```
+
+That's it. The agent gets meridian's coordination skills injected automatically
+and can start spawning work. In a separate shell, you can also drive spawns
+directly:
+
+```bash
+meridian spawn -m codex -p "Fix the flaky test in tests/auth/"
+meridian spawn list
+meridian spawn wait p1
+meridian spawn show p1
+```
+
+## Architecture
+
+```mermaid
+graph TB
+    User([You]) --> Primary["meridian<br/>(primary session)"]
+
+    subgraph Packages
+        Sources["git sources"] -->|"meridian mars add/sync"| Mars["mars"]
+        Mars --> Agents[".agents/"]
+        Agents -->|"meridian mars link"| Tool[".claude/ · .cursor/"]
+    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 + fs"]
+    end
+
+    Agents --> Primary
+    Primary --> State
+    Claude & Codex & OpenCode -->|"meridian CLI"| State
+```
+
+
+
+## Commands
+
+**Spawning & monitoring:**
+
+
+| Command                                  | Description                        |
+| ---------------------------------------- | ---------------------------------- |
+| `meridian`                               | Launch the primary agent session   |
+| `meridian spawn -a AGENT -p "task"`      | Delegate work to a routed model    |
+| `meridian spawn list`                    | See running and recent spawns      |
+| `meridian spawn wait ID`                 | Block until a spawn completes      |
+| `meridian spawn show ID`                 | Read a spawn's report              |
+| `meridian spawn --continue ID -p "more"` | Continue a prior spawn             |
+| `meridian spawn --from ID -p "next"`     | Start new spawn with prior context |
+
+
+**Reports & sessions:**
+
+
+| Command                           | Description                     |
+| --------------------------------- | ------------------------------- |
+| `meridian report search "query"`  | Search across all spawn reports |
+| `meridian session search "query"` | Search session transcripts      |
+
+
+**Configuration & diagnostics:**
+
+
+| Command                         | Description                                                           |
+| ------------------------------- | --------------------------------------------------------------------- |
+| `meridian init [--link DIR]`    | Initialize project (`.meridian/`, `mars.toml`, optional tool linking) |
+| `meridian config show`          | Show resolved config and bootstrap `.meridian/` on first run          |
+| `meridian config set KEY VALUE` | Set a config value                                                    |
+| `meridian models config show`   | Show `.meridian/models.toml` policy overrides                         |
+| `meridian models list`          | Inspect the model catalog                                             |
+| `meridian doctor`               | Run diagnostics                                                       |
+| `meridian serve`                | Start the MCP server                                                  |
+
+
+**Package management (mars):**
+
+
+| Command                    | Description                                  |
+| -------------------------- | -------------------------------------------- |
+| `meridian mars add SOURCE` | Add an agent/skill package source            |
+| `meridian mars sync`       | Resolve and install packages into `.agents/` |
+| `meridian mars link DIR`   | Symlink `.agents/` into a tool directory     |
+| `meridian mars list`       | Show installed agents and skills             |
+| `meridian mars upgrade`    | Fetch latest versions and sync               |
+
+
+## State Layout
+
+All state is files under `.meridian/` — no databases, no services. If it's not
+on disk, it doesn't exist.
+
+```
+.meridian/
+  .gitignore            # Tracks shared repo state, ignores machine-local state
+  spawns.jsonl          # Spawn event log
+  sessions.jsonl        # Session event log
+  spawns/
+    p1/
+      output.jsonl      # Spawn output
+      stderr.log        # Stderr capture
+      report.md         # Agent's report
+  fs/                   # Shared filesystem between spawns
+  work-items/           # Work item metadata
+  work/                 # Work item directories
+  work-archive/         # Completed work item scratch/docs
+  config.toml           # Repo configuration
+  models.toml           # Model aliases, routing, and visibility overrides
+```
+
+Writes use `fcntl.flock` plus atomic tmp+rename. If meridian is killed
+mid-spawn, the next read detects and reports the orphaned state.
+
+## Troubleshooting
+
+`**meridian` not found** — Run `uv tool update-shell` and restart your shell.
+
+`**meridian doctor` reports missing harnesses** — Install and authenticate at
+least one harness CLI (see Prerequisites).
+
+**Model routes to wrong harness** — Check `meridian models list` and
+`meridian config show`.
+
+**Spawn feels disconnected from earlier work** — Use `--continue ID` for
+session continuity, `--from ID` for context injection, or search past work
+with `meridian report search`.
+
+## Documentation
+
+- [Configuration](docs/configuration.md) — config keys, overrides, environment variables
+- [MCP Tools](docs/mcp-tools.md) — FastMCP tool surface and payload examples
+- [INSTALL.md](INSTALL.md) — agent-friendly install guide (give this URL to your LLM)
+
+## Development
+
+```bash
+uv sync --extra dev
+uv run ruff check .
+uv run pytest-llm
+uv run pyright
+```
+
+See [DEVELOPMENT.md](DEVELOPMENT.md) for full dev setup.
+
+## License
+
+[MIT](LICENSE)