coderouter-cli 2.7.8__tar.gz → 2.7.10__tar.gz

{coderouter_cli-2.7.8 → coderouter_cli-2.7.10}/CHANGELOG.md

@@ -9,9 +9,198 @@ are kept verbatim where the Japanese text itself is the subject).
 
 ---
 
+## [v2.7.10] — 2026-07-11 (agent_cli Phase 1c: antigravity — Phase 1 complete)
+
+Completes agent_cli Phase 1: `agent: antigravity` (the Google Antigravity
+CLI, command `agy`) is now implemented, joining `claude` (1a), `codex`
+(1b), and `grok` (1d) — all four Phase 1 backends are now in place. This
+target replaces the originally-planned `gemini`: on the author's Mac, the
+legacy Gemini CLI (`@google/gemini-cli` 0.50.x) now fails individual-account
+OAuth outright with a verified `IneligibleTierError: This client is no
+longer supported for Gemini Code Assist for individuals. To continue using
+Gemini, please migrate to the Antigravity suite of products:
+https://antigravity.google` (`reasonCode: UNSUPPORTED_CLIENT`,
+`tierId: free-tier`) — Google discontinued Gemini CLI for individual
+accounts on 2026-06-18. The same legacy CLI also still hits the
+trusted-directory gate with exit 55 (`--skip-trust` /
+`GEMINI_CLI_TRUST_WORKSPACE=true`), a pre-existing constraint unrelated to
+the discontinuation. Google's stated successor is the Antigravity CLI
+(`agy`) — a separate Go rewrite, not a fork of gemini-cli — which keeps
+individual Google-account OAuth alive, including the free tier. Verified
+against agy **1.1.1** (author's Mac, 2026-07-11), its flag surface differs
+meaningfully from gemini-cli's: no `--output-format json` (plain-text
+output only), `--mode plan|accept-edits` instead of an approval-mode flag,
+a `--dangerously-skip-permissions` full-bypass flag, a CLI-side
+`--print-timeout` (the first agent_cli target with its own timeout), no
+`--max-turns`, and no stdin channel for the prompt at all — piping stdin to
+`agy` hangs (field-verified). `agent: gemini` remains schema-declared but
+is now rejected with a migration-pointer message instead of a generic
+not-implemented one.
+
+### Added
+
+- **`agent: antigravity` builder/parser in `AgentCliAdapter`**
+  (`coderouter/adapters/agent_cli.py`) — invokes the Antigravity CLI
+  one-shot as `agy -p <prompt> --model <model> --mode plan --print-timeout
+  <exec_timeout_s>s` (read_only default). The prompt rides on argv as the
+  value of `-p` — agy has no `--prompt-file` equivalent and hangs if stdin
+  is piped (field-verified), so this is the fourth prompt-delivery pattern
+  among the four backends (claude/codex use stdin, grok uses
+  `--prompt-file`, antigravity uses argv). Documented limitation: Linux's
+  `MAX_ARG_STRLEN` (~128KiB) caps prompt size, and the prompt is visible in
+  `ps` output — there is no way around this with agy's current flag
+  surface. Output is plain text: stdout is decoded UTF-8, defensively
+  stripped of ANSI escapes, and trimmed; an empty result raises a
+  retryable `AdapterError`. There is no `--output-format json`, so token
+  usage, session id, and structured errors are all unavailable — usage is
+  reported as all zeros (same treatment as grok), and
+  `coderouter_session_id` is never populated.
+- **`sandbox_mode` → antigravity flag mapping** — `read_only` →
+  `--mode plan`; `edit` → `--mode accept-edits`; `full_auto` →
+  `--mode accept-edits --dangerously-skip-permissions`. As with the other
+  three backends, the effective mode is clamped to read-only whenever
+  `allow_file_writes=false`.
+- **`--print-timeout` as a CLI-side first wall** — generated from
+  `AgentCliConfig.exec_timeout_s` (e.g. `exec_timeout_s=600` →
+  `--print-timeout 600s`), letting agy self-terminate before the outer
+  `asyncio.wait_for` + process-group `SIGKILL` fires. antigravity is the
+  only agent_cli target with a double timeout wall.
+- **`max_turns` ignored for antigravity** — agy has no
+  `--max-turns`-equivalent flag; `AgentCliConfig.max_turns` has no effect
+  when `agent: antigravity`, same as codex.
+- **`command` defaults to `"agy"`** — the only agent_cli target whose
+  default executable name differs from the `agent` field value (the binary
+  is named for the CLI, not the product).
+- **5th `Literal` value on `AgentCliConfig.agent`** — `"antigravity"` joins
+  `claude`/`codex`/`gemini`/`grok`.
+
+### Changed
+
+- **`agent: gemini` now rejected with a migration message** instead of the
+  generic "not implemented yet" wording — constructing the adapter with
+  `agent: gemini` now raises `AdapterError: Google discontinued Gemini CLI
+  for individual accounts (June 2026). Use agent='antigravity' instead.`
+  (`retryable=False`).
+- **Schema docstrings** (`coderouter/config/schemas.py`) — `AgentCliConfig`
+  field descriptions updated for the four-backend reality
+  (claude/codex/antigravity/grok implemented, gemini rejected), including
+  the `command` and `max_turns` docstrings noting antigravity's `agy`
+  default and ignored `max_turns`.
+- **Docs & examples** — `docs/backends/external-agents.md`/`.en.md` gain a
+  full antigravity section (config example, adapter argv, the
+  argv-vs-stdin-vs-`--prompt-file` prompt-delivery comparison across all
+  four backends, mode mapping table, plain-text parsing and zero usage,
+  the `--print-timeout` double wall, OAuth setup with the `agy models`
+  smoke check, the display-string model-name caveat including that Claude
+  models are reachable through agy, the stdin-pipe-hang warning, and the
+  version-pin caveat) and lead with the gemini-discontinuation story
+  (updated implementation-status wording: Phase 1 complete, all four
+  backends). The design doc `docs/designs/external-agents-adapter.md` gets
+  a new appendix §11.5 recording the gemini-to-antigravity delta (body
+  text left as the historical record); its header status line now reads
+  Phase 1 (1a/1b/1c/1d) complete. `examples/providers-agent-cli.yaml`
+  replaces the Phase 1c gemini preview block with a documented (still
+  commented-out) antigravity block, with the now-empty
+  "unimplemented preview" framing removed since nothing remains
+  unimplemented.
+
+## [v2.7.9] — 2026-07-11 (agent_cli Phase 1b: codex)
+
+Adds the third target to the `agent_cli` adapter: `agent: codex` (the OpenAI
+Codex CLI) is now implemented alongside `claude` (Phase 1a) and `grok`
+(Phase 1d). The implementation was verified against the real CLI (codex-cli
+0.144.1, 2026-07-11), and one design-time assumption from the 2026-07
+research did not survive contact with it: `codex exec` has no approval flag
+at all (`-a`/`--ask-for-approval` doesn't exist in `exec --help` on
+0.144.1, since non-interactive execution has no approval prompt to control
+in the first place), so the design's separate `edit`/`full_auto` mappings
+(`-a on-request` / `-a never`) collapse into a single `-s workspace-write`
+mapping — unlike claude/grok, codex does not distinguish `edit` from
+`full_auto`. The verified JSONL `turn.completed.usage` payload also carries
+a field the design didn't record, `reasoning_output_tokens`, which is now
+normalized defensively into `completion_tokens_details.reasoning_tokens`.
+Everything else (stdin prompt delivery, `--skip-git-repo-check`,
+`--ephemeral`, the absence of `--max-turns`/`--timeout`, the ~8-day OAuth
+staleness) matched the design closely. `gemini` remains schema-declared but
+rejected (Phase 1c pending).
+
+### Added
+
+- **`agent: codex` builder/parser in `AgentCliAdapter`**
+  (`coderouter/adapters/agent_cli.py`) — invokes the Codex CLI one-shot as
+  `codex exec --json --skip-git-repo-check --ephemeral -m <model>
+  -C <workdir> -s read-only -` (read_only default). The prompt is delivered
+  on stdin with an explicit trailing `-` sentinel — the same channel as
+  claude, unlike grok's `--prompt-file` delivery. Output is JSONL on
+  stdout (progress goes to stderr); the final answer is the `item.text` of
+  the **last** `item.completed` event whose `item.type=="agent_message"`.
+  Usage comes from `turn.completed.usage` and is normalized as
+  `prompt_tokens=input_tokens` / `completion_tokens=output_tokens`, with
+  `cached_input_tokens` kept as `prompt_tokens_details.cached_tokens` (a
+  subset of `input_tokens`, not added on top — verified 13810 ⊃ 9984) and
+  `reasoning_output_tokens` kept as
+  `completion_tokens_details.reasoning_tokens` when nonzero; multiple
+  `turn.completed` events, if seen, are summed. `thread_id` (from
+  `thread.started`) surfaces as `coderouter_session_id`. Parsing is
+  defensive line-by-line — a non-JSON line doesn't abort the rest of the
+  stream, but no valid `agent_message` (or empty stdout) raises a
+  retryable `AdapterError`, as does any `error` event or `turn.failed`.
+  The CLI is pre-1.0 and `--json`'s alias is still `--experimental-json`
+  (schema not frozen), so version pinning is recommended alongside the
+  defensive parsing.
+- **`sandbox_mode` → codex flag mapping** — `read_only` → `-s read-only`;
+  `edit` → `-s workspace-write`; `full_auto` → `-s workspace-write` (same
+  as `edit` — `exec` has no approval flag in 0.144.1, and
+  `--dangerously-bypass-approvals-and-sandbox` is never used). As with
+  claude/grok, the effective mode is clamped to read-only whenever
+  `allow_file_writes=false`, regardless of `sandbox_mode`.
+- **`--skip-git-repo-check` always passed** — CodeRouter's isolated workdir
+  is never a git repository, and codex's default "trusted directory" check
+  fails immediately outside one (exit 1, stderr `Not inside a trusted
+  directory and --skip-git-repo-check was not specified.` — field-verified).
+  The adapter always passes this flag, so that error should never surface
+  in normal operation.
+- **`--ephemeral` always passed** — prevents the session from persisting to
+  disk, for the same stateless-transformation rationale as grok's
+  `--no-memory`. Not configurable.
+- **`max_turns` ignored for codex** — `codex exec` has neither
+  `--max-turns` nor `--timeout`; `AgentCliConfig.max_turns` has no effect
+  when `agent: codex`, and `exec_timeout_s` + process-group `SIGKILL` is
+  the only time bound.
+- **`coderouter_session_id` via `thread_id`** — same response-metadata
+  treatment as claude's `session_id` and grok's `sessionId`.
+
+### Changed
+
+- **Unsupported-agent error message** — constructing the adapter with a
+  not-yet-implemented agent now lists all three implemented agents (e.g.
+  `agent 'gemini' is not implemented yet (implemented: claude, codex,
+  grok)`) instead of the two-agent wording from v2.7.8.
+- **Schema docstrings** (`coderouter/config/schemas.py`) — `AgentCliConfig`
+  field descriptions updated for the three-agent reality, including the
+  `max_turns` docstring noting codex ignores it.
+- **Docs & examples** — `docs/backends/external-agents.md`/`.en.md` gain a
+  full codex section (config example, adapter argv, stdin-vs-`--prompt-file`
+  contrast with grok, sandbox mapping table with the no-approval-flag-in-exec
+  note, JSONL schema and usage normalization including
+  `reasoning_output_tokens`, OAuth setup with the ~8-day staleness caveat
+  and `CODEX_API_KEY`/`OPENAI_API_KEY`/`CODEX_HOME`, and the pre-1.0
+  version-pin caveat) and updated implementation-status wording (claude +
+  codex + grok implemented; gemini-only rejected). The design doc
+  `docs/designs/external-agents-adapter.md` gets a new appendix §11.4
+  recording the verified deltas between the 2026-07 research and
+  codex-cli 0.144.1 (body text left as the historical record); its header
+  status line now lists Phase 1b alongside 1a/1d.
+  `examples/providers-agent-cli.yaml` promotes codex out of the
+  not-implemented preview into a documented (still commented-out, so
+  copying the file doesn't require codex to be installed) block with
+  `model: gpt-5.5`, `paid: false` for subscription OAuth, and
+  `passthrough_env: []`; the preview section at the bottom is retitled to
+  Phase 1c (gemini only), with codex removed from it.
+
 ## [v2.7.8] — 2026-07-10 (agent_cli Phase 1d: grok)
 
-Adds the second target to the `agent_cli` adapter: `agent: grok` (the xAI
+**PR #68**. Adds the second target to the `agent_cli` adapter: `agent: grok` (the xAI
 Grok CLI) is now implemented alongside `claude` from Phase 1a. The
 implementation was verified against the real CLI (grok v0.2.93, [stable]
 channel, 2026-07-10), and several design-time assumptions from the 2026-07

{coderouter_cli-2.7.8 → coderouter_cli-2.7.10}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: coderouter-cli
-Version: 2.7.8
+Version: 2.7.10
 Summary: Local-first, free-first, fallback-built-in LLM router. Claude Code / OpenAI compatible.
 Project-URL: Homepage, https://github.com/zephel01/CodeRouter
 Project-URL: Repository, https://github.com/zephel01/CodeRouter