cli-relay 0.1.0__tar.gz

cli_relay-0.1.0/.gitignore

@@ -0,0 +1,15 @@
+__pycache__/
+*.py[cod]
+.venv/
+build/
+dist/
+*.egg-info/
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+.coverage
+htmlcov/
+/cli-relay.toml
+/HANDOFF.md
+.env
+.venv-*/

cli_relay-0.1.0/CHANGELOG.md

@@ -0,0 +1,35 @@
+# Changelog
+
+All notable changes to this project are documented here. The format follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and the project uses
+[Semantic Versioning](https://semver.org/).
+
+## [Unreleased]
+
+## [0.1.0] - 2026-11-15
+
+### Added
+- `Relay`: runs a task on the first available provider and falls back on rate limits,
+  auth errors, missing CLIs and generic errors (configurable).
+- Adapters for Claude Code (`claude -p --output-format stream-json`), Google Antigravity
+  (`agy -p --output-format stream-json`) and any OpenAI-compatible chat endpoint.
+- Adapter for OpenAI Codex (`codex exec --json`); on Windows it also finds the `codex.exe`
+  bundled with the Codex desktop app. Command layout and the rate-limit path are verified
+  against codex-cli 0.167.
+- Reset times are parsed from "in 2h 30m", wall-clock ("try again at 11:05 AM",
+  "resets 3pm") and epoch formats.
+- Normalised event stream: `started`, `text_delta`, `tool_activity`, `quota_info`,
+  `completed`, `failed`, `skipped`, `waiting`, `switched`.
+- Persistent quota tracker: remembers limits and reset times; skips a provider
+  pre-emptively when a reported usage window is nearly exhausted.
+- Mid-task handoff: the next provider receives the original task, actions taken and the
+  last output, plus an instruction to inspect the working tree first.
+- Permission levels (`read_only`, `edit`, `full`) mapped to each CLI's own flags, with a
+  per-provider upper bound.
+- `cli-relay` command (`run`, `status`, `reset`, `mcp`) with text and NDJSON output.
+- MCP server (`cli-relay[mcp]`) with `relay_run` and `relay_status` tools. Permissions
+  requested over MCP are capped by `[mcp] max_permission` (default `read_only`).
+- TOML configuration.
+
+[Unreleased]: https://github.com/mustikon/cli-relay/compare/v0.1.0...HEAD
+[0.1.0]: https://github.com/mustikon/cli-relay/releases/tag/v0.1.0

cli_relay-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 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 [yyyy] [name of copyright owner]
+
+   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.

cli_relay-0.1.0/PKG-INFO

@@ -0,0 +1,227 @@
+Metadata-Version: 2.5
+Name: cli-relay
+Version: 0.1.0
+Summary: Run coding-agent CLIs (Claude Code, Antigravity, Codex, any OpenAI-compatible API) as one worker with automatic fallback when a subscription hits its limit.
+Project-URL: Homepage, https://github.com/mustikon/cli-relay
+Project-URL: Issues, https://github.com/mustikon/cli-relay/issues
+Project-URL: Changelog, https://github.com/mustikon/cli-relay/blob/main/CHANGELOG.md
+Author: mustikon
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: agents,antigravity,claude-code,codex,fallback,gemini,llm,mcp,rate-limit
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Provides-Extra: mcp
+Requires-Dist: mcp<2,>=1.10; extra == 'mcp'
+Description-Content-Type: text/markdown
+
+# cli-relay
+
+[![CI](https://github.com/mustikon/cli-relay/actions/workflows/ci.yml/badge.svg)](https://github.com/mustikon/cli-relay/actions/workflows/ci.yml)
+[![PyPI](https://img.shields.io/pypi/v/cli-relay.svg)](https://pypi.org/project/cli-relay/)
+[![Python](https://img.shields.io/pypi/pyversions/cli-relay.svg)](https://pypi.org/project/cli-relay/)
+[![License](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](LICENSE)
+
+**One worker interface over several coding-agent CLIs, with automatic fallback when a
+subscription hits its limit.**
+
+[Русская версия](README.ru.md)
+
+You pay for Claude, ChatGPT and Google subscriptions, and each comes with its own agent CLI
+and its own usage window. `cli-relay` runs a task on the first provider that can take it.
+If that provider runs out of quota mid-task, the relay hands the work to the next one with
+a briefing on what was already done.
+
+```
+cli-relay run "fix the failing test in tests/test_api.py" --cwd ~/code/app --permission edit
+
+[cli-relay] claude started (claude-opus-5-5)
+...
+[cli-relay] claude failed [rate_limit]: You've hit your limit · resets 3pm
+[cli-relay] switching claude -> antigravity (rate_limit)
+[cli-relay] antigravity started
+...
+[cli-relay] done by antigravity
+```
+
+## Why
+
+* **The official CLIs, unmodified.** `cli-relay` launches `claude`, `agy` and `codex`
+  exactly as you would, under your own login. It never extracts, proxies or reuses OAuth
+  tokens. You keep each tool's own permissions, hooks, `CLAUDE.md` / `AGENTS.md`, skills
+  and MCP servers.
+* **Limit-aware.** Claude Code reports its five-hour and weekly windows in its event
+  stream. `cli-relay` records them and skips a provider *before* it fails when a window is
+  nearly used up. A provider that failed on a limit is skipped until its reset time.
+* **Handoff, not restart.** When it switches providers mid-task, the next agent gets the
+  original task, the actions already taken and the last output. It is also told to check
+  `git status` / `git diff` before continuing.
+* **One event stream.** Every provider is normalised to the same events (`started`,
+  `text_delta`, `tool_activity`, `quota_info`, `completed`, `failed`, plus the relay's
+  `skipped` / `waiting` / `switched`). Use `--format ndjson` to drive it from another
+  program, such as a voice assistant.
+* **MCP server.** `cli-relay mcp` exposes `relay_run` and `relay_status`, so any MCP client
+  can delegate work and get fallback for free.
+* **Small and dependency-free.** The core uses only the Python standard library. That
+  matters for a tool that runs next to all your credentials.
+
+## Providers
+
+| Type | CLI / endpoint | Status | Session resume | Quota telemetry |
+|---|---|---|---|---|
+| `claude` | Claude Code `claude -p --output-format stream-json` | verified live | `--resume` | five-hour / weekly windows |
+| `antigravity` | Google Antigravity `agy -p --output-format stream-json` | verified live | `--conversation` | from error text |
+| `codex` | OpenAI Codex `codex exec --json` (also finds the copy bundled with the Codex desktop app on Windows) | command layout and limit path verified live on 0.167; success path from docs | `exec resume` | from error text, incl. "try again at 11:05 AM" |
+| `openai` | any OpenAI-compatible `/chat/completions` (OpenRouter, vLLM, Ollama, LM Studio…) | tested with a local server | — | HTTP 429 + `Retry-After` |
+
+The `openai` type is a **text-only** fallback: it has no tools and cannot edit files.
+
+## Install
+
+```bash
+pipx install cli-relay            # or: uv tool install cli-relay
+pipx install "cli-relay[mcp]"     # with the MCP server
+```
+
+Requires Python 3.11+. Install and log in to the agent CLIs you want to use first.
+
+## Usage
+
+```bash
+cli-relay status                                   # what is installed / limited
+cli-relay run "explain src/auth.py"                # read-only by default
+cli-relay run - < task.md --cwd ./repo --permission edit
+cli-relay run "continue" --resume claude=SESSION_ID
+cli-relay run "..." --providers antigravity,claude --format ndjson
+cli-relay reset [provider]                         # forget recorded limits
+```
+
+### Permissions
+
+`--permission` is mapped to each CLI's own permission system. Non-interactive runs never
+wait for a prompt: anything that would ask is denied.
+
+| `--permission` | Claude Code | Antigravity | Codex |
+|---|---|---|---|
+| `read_only` (default) | `--permission-mode dontAsk` | `--mode plan` | `--sandbox read-only` |
+| `edit` | `--permission-mode acceptEdits` | `--mode accept-edits` | `--sandbox workspace-write` |
+| `full` | `--permission-mode auto` | `--mode auto` | `workspace-write` + `--approve-for-me` |
+
+A provider's `permission` setting is an upper bound, so a task never gets more than that.
+`cli-relay` never uses "skip all permission checks" flags.
+
+## Configuration
+
+`cli-relay` looks for its config file in this order:
+
+1. `--config PATH`
+2. `$CLI_RELAY_CONFIG`
+3. `./cli-relay.toml`
+4. `%APPDATA%\cli-relay\config.toml` on Windows, `~/.config/cli-relay/config.toml` elsewhere
+
+Without a file the chain is `claude → antigravity → codex`. See
+[`examples/cli-relay.toml`](examples/cli-relay.toml):
+
+```toml
+order = ["claude", "antigravity", "codex", "openrouter", "local"]
+
+[relay]
+wait_if_reset_within_s = 900      # wait for a provider that resets within 15 min
+skip_above_utilization = 0.97     # skip Claude when a usage window is ≥ 97 %
+default_cooldown_s = 1800         # when a limit error carries no reset time
+write_handoff_file = false        # also write HANDOFF.md into --cwd on a switch
+
+[providers.claude]
+model = "opus"
+permission = "edit"               # upper bound for this provider
+
+[providers.openrouter]
+type = "openai"
+base_url = "https://openrouter.ai/api/v1"
+model = "vendor/model-id"          # any OpenRouter model id
+api_key_env = "OPENROUTER_API_KEY"
+
+[providers.local]
+type = "openai"
+base_url = "http://127.0.0.1:8000/v1"   # vLLM / Ollama / LM Studio
+model = "your-served-model-name"
+```
+
+Recorded limits live in `%LOCALAPPDATA%\cli-relay\state.json` on Windows and
+`~/.local/state/cli-relay/state.json` elsewhere. Override the path with `$CLI_RELAY_STATE`.
+
+## As an MCP server
+
+```bash
+claude mcp add cli-relay -- cli-relay mcp
+```
+
+The server exposes two tools:
+* `relay_run(prompt, cwd?, providers?, permission?)` returns `{ok, provider, text, session_id, switches, skipped}`.
+* `relay_status()` returns installed providers and their known limits.
+
+By default an MCP client can only request `read_only` work, whatever it asks for.
+Otherwise a sandboxed agent could escalate by delegating to another one. To allow more,
+set this in the config:
+
+```toml
+[mcp]
+max_permission = "edit"
+```
+
+## As a library
+
+```python
+import asyncio
+from cli_relay import Relay, Task, TextDelta, Completed
+from cli_relay.config import load
+
+async def main() -> None:
+    cfg = load()
+    relay = Relay(cfg.adapters(), cfg.quota(), cfg.policy)
+    async for event in relay.run(Task(prompt="summarise README.md")):
+        if isinstance(event, TextDelta):
+            print(event.text, end="")
+        elif isinstance(event, Completed):
+            print(f"\n-- by {event.provider}")
+
+asyncio.run(main())
+```
+
+## Terms of service
+
+`cli-relay` is meant for **your own** subscriptions on **your own** machine. It runs each
+vendor's official CLI as a normal user would, and the vendors' terms still apply. For
+unattended automation, the vendors recommend API keys over subscription logins. Do not
+use `cli-relay` to share one subscription between several people.
+
+## Security notes
+
+* Agent processes are started from an argument list, never through a shell.
+* On Windows, `claude` and `codex` are npm `.cmd` shims, which `cmd.exe` re-parses. Prompts
+  and system prompts are therefore always sent through stdin or a temp file. `cli-relay`
+  refuses to put `cmd.exe` metacharacters on such a command line.
+* Corrupted or interleaved NDJSON lines are salvaged rather than crashing a long run.
+
+See [SECURITY.md](SECURITY.md) for how to report a vulnerability.
+
+## Roadmap
+
+- Voice and push approvals for permission prompts (Claude Code `PermissionRequest` hook,
+  Codex app-server approvals)
+- Codex app-server adapter with first-class rate-limit telemetry
+- Git worktree per task with automatic WIP checkpoints
+- Same-harness fallback (Claude Code against an Anthropic-compatible endpoint)
+
+## License
+
+[Apache-2.0](LICENSE)

cli_relay-0.1.0/README.md

@@ -0,0 +1,201 @@
+# cli-relay
+
+[![CI](https://github.com/mustikon/cli-relay/actions/workflows/ci.yml/badge.svg)](https://github.com/mustikon/cli-relay/actions/workflows/ci.yml)
+[![PyPI](https://img.shields.io/pypi/v/cli-relay.svg)](https://pypi.org/project/cli-relay/)
+[![Python](https://img.shields.io/pypi/pyversions/cli-relay.svg)](https://pypi.org/project/cli-relay/)
+[![License](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](LICENSE)
+
+**One worker interface over several coding-agent CLIs, with automatic fallback when a
+subscription hits its limit.**
+
+[Русская версия](README.ru.md)
+
+You pay for Claude, ChatGPT and Google subscriptions, and each comes with its own agent CLI
+and its own usage window. `cli-relay` runs a task on the first provider that can take it.
+If that provider runs out of quota mid-task, the relay hands the work to the next one with
+a briefing on what was already done.
+
+```
+cli-relay run "fix the failing test in tests/test_api.py" --cwd ~/code/app --permission edit
+
+[cli-relay] claude started (claude-opus-5-5)
+...
+[cli-relay] claude failed [rate_limit]: You've hit your limit · resets 3pm
+[cli-relay] switching claude -> antigravity (rate_limit)
+[cli-relay] antigravity started
+...
+[cli-relay] done by antigravity
+```
+
+## Why
+
+* **The official CLIs, unmodified.** `cli-relay` launches `claude`, `agy` and `codex`
+  exactly as you would, under your own login. It never extracts, proxies or reuses OAuth
+  tokens. You keep each tool's own permissions, hooks, `CLAUDE.md` / `AGENTS.md`, skills
+  and MCP servers.
+* **Limit-aware.** Claude Code reports its five-hour and weekly windows in its event
+  stream. `cli-relay` records them and skips a provider *before* it fails when a window is
+  nearly used up. A provider that failed on a limit is skipped until its reset time.
+* **Handoff, not restart.** When it switches providers mid-task, the next agent gets the
+  original task, the actions already taken and the last output. It is also told to check
+  `git status` / `git diff` before continuing.
+* **One event stream.** Every provider is normalised to the same events (`started`,
+  `text_delta`, `tool_activity`, `quota_info`, `completed`, `failed`, plus the relay's
+  `skipped` / `waiting` / `switched`). Use `--format ndjson` to drive it from another
+  program, such as a voice assistant.
+* **MCP server.** `cli-relay mcp` exposes `relay_run` and `relay_status`, so any MCP client
+  can delegate work and get fallback for free.
+* **Small and dependency-free.** The core uses only the Python standard library. That
+  matters for a tool that runs next to all your credentials.
+
+## Providers
+
+| Type | CLI / endpoint | Status | Session resume | Quota telemetry |
+|---|---|---|---|---|
+| `claude` | Claude Code `claude -p --output-format stream-json` | verified live | `--resume` | five-hour / weekly windows |
+| `antigravity` | Google Antigravity `agy -p --output-format stream-json` | verified live | `--conversation` | from error text |
+| `codex` | OpenAI Codex `codex exec --json` (also finds the copy bundled with the Codex desktop app on Windows) | command layout and limit path verified live on 0.167; success path from docs | `exec resume` | from error text, incl. "try again at 11:05 AM" |
+| `openai` | any OpenAI-compatible `/chat/completions` (OpenRouter, vLLM, Ollama, LM Studio…) | tested with a local server | — | HTTP 429 + `Retry-After` |
+
+The `openai` type is a **text-only** fallback: it has no tools and cannot edit files.
+
+## Install
+
+```bash
+pipx install cli-relay            # or: uv tool install cli-relay
+pipx install "cli-relay[mcp]"     # with the MCP server
+```
+
+Requires Python 3.11+. Install and log in to the agent CLIs you want to use first.
+
+## Usage
+
+```bash
+cli-relay status                                   # what is installed / limited
+cli-relay run "explain src/auth.py"                # read-only by default
+cli-relay run - < task.md --cwd ./repo --permission edit
+cli-relay run "continue" --resume claude=SESSION_ID
+cli-relay run "..." --providers antigravity,claude --format ndjson
+cli-relay reset [provider]                         # forget recorded limits
+```
+
+### Permissions
+
+`--permission` is mapped to each CLI's own permission system. Non-interactive runs never
+wait for a prompt: anything that would ask is denied.
+
+| `--permission` | Claude Code | Antigravity | Codex |
+|---|---|---|---|
+| `read_only` (default) | `--permission-mode dontAsk` | `--mode plan` | `--sandbox read-only` |
+| `edit` | `--permission-mode acceptEdits` | `--mode accept-edits` | `--sandbox workspace-write` |
+| `full` | `--permission-mode auto` | `--mode auto` | `workspace-write` + `--approve-for-me` |
+
+A provider's `permission` setting is an upper bound, so a task never gets more than that.
+`cli-relay` never uses "skip all permission checks" flags.
+
+## Configuration
+
+`cli-relay` looks for its config file in this order:
+
+1. `--config PATH`
+2. `$CLI_RELAY_CONFIG`
+3. `./cli-relay.toml`
+4. `%APPDATA%\cli-relay\config.toml` on Windows, `~/.config/cli-relay/config.toml` elsewhere
+
+Without a file the chain is `claude → antigravity → codex`. See
+[`examples/cli-relay.toml`](examples/cli-relay.toml):
+
+```toml
+order = ["claude", "antigravity", "codex", "openrouter", "local"]
+
+[relay]
+wait_if_reset_within_s = 900      # wait for a provider that resets within 15 min
+skip_above_utilization = 0.97     # skip Claude when a usage window is ≥ 97 %
+default_cooldown_s = 1800         # when a limit error carries no reset time
+write_handoff_file = false        # also write HANDOFF.md into --cwd on a switch
+
+[providers.claude]
+model = "opus"
+permission = "edit"               # upper bound for this provider
+
+[providers.openrouter]
+type = "openai"
+base_url = "https://openrouter.ai/api/v1"
+model = "vendor/model-id"          # any OpenRouter model id
+api_key_env = "OPENROUTER_API_KEY"
+
+[providers.local]
+type = "openai"
+base_url = "http://127.0.0.1:8000/v1"   # vLLM / Ollama / LM Studio
+model = "your-served-model-name"
+```
+
+Recorded limits live in `%LOCALAPPDATA%\cli-relay\state.json` on Windows and
+`~/.local/state/cli-relay/state.json` elsewhere. Override the path with `$CLI_RELAY_STATE`.
+
+## As an MCP server
+
+```bash
+claude mcp add cli-relay -- cli-relay mcp
+```
+
+The server exposes two tools:
+* `relay_run(prompt, cwd?, providers?, permission?)` returns `{ok, provider, text, session_id, switches, skipped}`.
+* `relay_status()` returns installed providers and their known limits.
+
+By default an MCP client can only request `read_only` work, whatever it asks for.
+Otherwise a sandboxed agent could escalate by delegating to another one. To allow more,
+set this in the config:
+
+```toml
+[mcp]
+max_permission = "edit"
+```
+
+## As a library
+
+```python
+import asyncio
+from cli_relay import Relay, Task, TextDelta, Completed
+from cli_relay.config import load
+
+async def main() -> None:
+    cfg = load()
+    relay = Relay(cfg.adapters(), cfg.quota(), cfg.policy)
+    async for event in relay.run(Task(prompt="summarise README.md")):
+        if isinstance(event, TextDelta):
+            print(event.text, end="")
+        elif isinstance(event, Completed):
+            print(f"\n-- by {event.provider}")
+
+asyncio.run(main())
+```
+
+## Terms of service
+
+`cli-relay` is meant for **your own** subscriptions on **your own** machine. It runs each
+vendor's official CLI as a normal user would, and the vendors' terms still apply. For
+unattended automation, the vendors recommend API keys over subscription logins. Do not
+use `cli-relay` to share one subscription between several people.
+
+## Security notes
+
+* Agent processes are started from an argument list, never through a shell.
+* On Windows, `claude` and `codex` are npm `.cmd` shims, which `cmd.exe` re-parses. Prompts
+  and system prompts are therefore always sent through stdin or a temp file. `cli-relay`
+  refuses to put `cmd.exe` metacharacters on such a command line.
+* Corrupted or interleaved NDJSON lines are salvaged rather than crashing a long run.
+
+See [SECURITY.md](SECURITY.md) for how to report a vulnerability.
+
+## Roadmap
+
+- Voice and push approvals for permission prompts (Claude Code `PermissionRequest` hook,
+  Codex app-server approvals)
+- Codex app-server adapter with first-class rate-limit telemetry
+- Git worktree per task with automatic WIP checkpoints
+- Same-harness fallback (Claude Code against an Anthropic-compatible endpoint)
+
+## License
+
+[Apache-2.0](LICENSE)