From 0c611bbd65305b3457b485544f70a2462b2aace5 Mon Sep 17 00:00:00 2001 From: Claude Date: Fri, 6 Nov 2026 22:36:30 +0000 Subject: [PATCH 1/2] AGENTS.md: route Gemini 4 Argon through Paseo's antigravity provider (slim-down C3) The agy TUI is retired (2026-11-06, E9). Route 3 and the Carbon recheck use paseo run / paseo provider models; acp-dispatch noted as a shim. Co-Authored-By: Claude Sonnet 5.5 Claude-Session: https://claude.ai/code/session_01BvGHM3M9bXWXHwGGHz6Ctd --- AGENTS.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 17a6df9..405875a 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -32,7 +32,7 @@ djbclark, 2026-10-31: tendcf and nix2cf are the most important work he is doing, and getting it right outranks cost. This lifts `model-routing` item 1b's *reason* test for these two repos only: here a frontier review needs no "really needs a frontier model" case, and a second opinion is reason enough. Every -other repo keeps the default. The mechanics stay (item 4): `acp-dispatch`'s +other repo keeps the default. The mechanics stay (item 4). As of 2026-11-06 (slim-down) `acp-dispatch` is a shim over `paseo run` and will be replaced by `paseo run` lines in a follow-up; `acp-dispatch`'s estimate floors, per-wave caps, in-flight reservation and exit 5 are not overridden. Never use `route-override`, `--est-pct`, `--min-headroom 0` or `--no-preflight` to get around them. @@ -46,7 +46,7 @@ overridden. Never use `route-override`, `--est-pct`, `--min-headroom 0` or 2. **Models.** Every lead session runs Opus 5.5 `high`, pipeline-only sessions (merges, waiters) included; `[lead].pipeline_model` does not apply here. Never Sonnet as a lead, and Fable is never a lead. Code slices run on - Sonnet 5.5 `high` or better (agy's Opus pool is fine) on whichever pool + Sonnet 5.5 `high` or better (the antigravity provider's Opus pool is fine) on whichever pool `route_agent.py plan` picks, through `/bigteam`. Never use a weaker tier (GLM, Gemini Flash, Cursor Auto, `gpt-6-luna`) in these repos. A slice climbs a tier only on evidence of failure. @@ -61,7 +61,7 @@ overridden. Never use `route-override`, `--est-pct`, `--min-headroom 0` or order: 1. astra: `acp-dispatch codex --model gpt-6-astra --kind frontier --effort high --perm read-only --frontier-reason " standing rule: cross-model review" --name NAME -f BRIEF -C WORKTREE` 2. Fable: `acp-dispatch claude --model fable --kind frontier --effort high --perm read-only --frontier-reason "..." --name NAME -f BRIEF -C WORKTREE` - 3. Gemini 4 Argon: `acp-dispatch agy --model gemini-4-argon --kind frontier --effort high --perm all --frontier-reason " standing rule: cross-model review" --name NAME -f BRIEF -C WORKTREE`. acp-run has no verified read-only mode for agy, so put read-only instructions in BRIEF and check the worktree diff before and after the review. That restricts Argon by instruction only, not by a read-only sandbox. Argon is fallback-only: it stands in when astra or Fable is short. Its frontier wiring landed in djbclark-ade PR 224 (merged 2026-11-02). + 3. Gemini 4 Argon (a Paseo run since 2026-11-06; the agy TUI is retired, slim-down E9, and the Google AI plan is reached through Paseo's antigravity provider): `paseo run --provider antigravity --model gemini-4-argon --no-wait --title NAME --cwd WORKTREE "$(cat BRIEF)"`. `paseo run` takes the brief as its positional prompt (it has no `--prompt-file`; `paseo send` does), so BRIEF is read in by the shell. End BRIEF with the report path ("write your full report to REPORT_PATH") and read that file after `paseo wait AGENT_ID`. The old `--perm all` is `--mode`, whose ids are provider-specific: pass the antigravity provider's full-access mode only after confirming its id (not verified 2026-11-06); there is no verified read-only mode, so put read-only instructions in BRIEF and check the worktree diff before and after the review. That restricts Argon by instruction only, not by a read-only sandbox. Argon is fallback-only: it stands in when astra or Fable is short. Its frontier wiring landed in djbclark-ade PR 224 (merged 2026-11-02); a `paseo run` bypasses `acp-dispatch`'s preflight, so check the Google pool with `aiuse --available --json` first. - A pool is **short** when `acp-dispatch` answers exit 5 (`unavailable`: wont-fit, inflight, headroom or preflight), or when `aiuse --available --json` lists it `usable_now: false`. Argon with no fresh `aiuse` reading counts @@ -113,6 +113,7 @@ overridden. Never use `route-override`, `--est-pct`, `--min-headroom 0` or window on 2026-10-18). Every astra, Fable or Argon review goes through `acp-dispatch --kind frontier`, never a hand-run `acp-run`. 5. **Gemini 4 Carbon** (announced 2026-10-28, not yet reachable by us): - recheck weekly with `acp-run agy --info --model gemini-4-carbon` and + recheck weekly with `paseo provider models antigravity` (the agy TUI + and `acp-run agy --info` are retired as of 2026-11-06, slim-down E9) and `aiuse --available --json`. When it is reachable, adopt it as the Google frontier model in place of Argon. From 3d34a549b26de008fceb23175c9c25d1a9682138 Mon Sep 17 00:00:00 2001 From: Claude Date: Fri, 6 Nov 2026 22:39:49 +0000 Subject: [PATCH 2/2] AGENTS.md: Argon route stays behind acp-dispatch --kind frontier (Codex P1); the agent name becomes the Paseo provider when the slim-down lands --- AGENTS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/AGENTS.md b/AGENTS.md index 405875a..dd60c05 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -61,7 +61,7 @@ overridden. Never use `route-override`, `--est-pct`, `--min-headroom 0` or order: 1. astra: `acp-dispatch codex --model gpt-6-astra --kind frontier --effort high --perm read-only --frontier-reason " standing rule: cross-model review" --name NAME -f BRIEF -C WORKTREE` 2. Fable: `acp-dispatch claude --model fable --kind frontier --effort high --perm read-only --frontier-reason "..." --name NAME -f BRIEF -C WORKTREE` - 3. Gemini 4 Argon (a Paseo run since 2026-11-06; the agy TUI is retired, slim-down E9, and the Google AI plan is reached through Paseo's antigravity provider): `paseo run --provider antigravity --model gemini-4-argon --no-wait --title NAME --cwd WORKTREE "$(cat BRIEF)"`. `paseo run` takes the brief as its positional prompt (it has no `--prompt-file`; `paseo send` does), so BRIEF is read in by the shell. End BRIEF with the report path ("write your full report to REPORT_PATH") and read that file after `paseo wait AGENT_ID`. The old `--perm all` is `--mode`, whose ids are provider-specific: pass the antigravity provider's full-access mode only after confirming its id (not verified 2026-11-06); there is no verified read-only mode, so put read-only instructions in BRIEF and check the worktree diff before and after the review. That restricts Argon by instruction only, not by a read-only sandbox. Argon is fallback-only: it stands in when astra or Fable is short. Its frontier wiring landed in djbclark-ade PR 224 (merged 2026-11-02); a `paseo run` bypasses `acp-dispatch`'s preflight, so check the Google pool with `aiuse --available --json` first. + 3. Gemini 4 Argon: `acp-dispatch agy --model gemini-4-argon --kind frontier --effort high --perm all --frontier-reason " standing rule: cross-model review" --name NAME -f BRIEF -C WORKTREE` today; when the djbclark-ade slim-down lands (its E9 retires the agy TUI and the Google AI plan is reached through Paseo's antigravity provider; its E6 shim maps the agent name to the Paseo provider) the same line reads `acp-dispatch antigravity --model gemini-4-argon …`. Argon stays behind `acp-dispatch --kind frontier` (estimate floor, in-flight reservation, per-wave frontier cap, exit 5), never a bare `paseo run`. There is no verified read-only mode for the Google provider, so put read-only instructions in BRIEF and check the worktree diff before and after the review. That restricts Argon by instruction only, not by a read-only sandbox. Argon is fallback-only: it stands in when astra or Fable is short. Its frontier wiring landed in djbclark-ade PR 224 (merged 2026-11-02). - A pool is **short** when `acp-dispatch` answers exit 5 (`unavailable`: wont-fit, inflight, headroom or preflight), or when `aiuse --available --json` lists it `usable_now: false`. Argon with no fresh `aiuse` reading counts