Repository navigation
AGENTS.md: frontier route 3 via Paseo's antigravity provider; acp-dispatch is a shim (djbclark-ade slim-down C3) - #6
Conversation
…(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 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BvGHM3M9bXWXHwGGHz6Ctd
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: 6e8b848f-d6fb-41a0-bd39-67ccfdb09d39) |
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 0c611bbd65
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| 1. astra: `acp-dispatch codex --model gpt-6-astra --kind frontier --effort high --perm read-only --frontier-reason "<repo> 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 "<repo> 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. |
There was a problem hiding this comment.
Preserve guarded dispatch for the Argon fallback
When astra or Fable is short, this replacement directs the reviewer to launch Argon through paseo run instead of the mandatory acp-dispatch --kind frontier path. Checking aiuse --available --json first does not preserve the required estimate-floor, in-flight reservation, and per-wave frontier-cap checks. The new fallback therefore bypasses safeguards that this same document explicitly says remain mandatory. Keep Argon behind guarded dispatch, or provide an equivalent guarded replacement before directing sessions to use it.
AGENTS.md reference: AGENTS.md:L109-L114
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Confirmed and fixed in 3d34a54. Route 3 stays behind acp-dispatch --kind frontier (estimate floor, in-flight reservation, per-wave cap, exit 5): it reads acp-dispatch agy … today and acp-dispatch antigravity … once the djbclark-ade slim-down lands, whose acp-dispatch shim maps the agent name to the Paseo provider. The bare paseo run line and the aiuse --available --json substitute are gone.
Generated by Claude Code
…ex P1); the agent name becomes the Paseo provider when the slim-down lands
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: 562859ad-c05b-4570-9427-0ee7481a43fe) |
|
@codex review Generated by Claude Code |
🛡️ Codex Security Review · Automatically triggeredSecurity review completed. No security issues were found in this pull request. Reviewed commit: Only the user who started this review can view the report in Codex. ℹ️ About Codex security reviews in GitHubThis is an experimental Codex feature. Security reviews are triggered when:
Once complete, Codex will leave suggestions, or a comment if no findings are found. |
|
Codex Review: Didn't find any major issues. 🚀 Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
djbclark-ade's slim-down (
docs/slim/PLAN.md, C3 per-file migration, J2b) retires the agy TUI on 2026-11-06; the Google AI plan is reached through Paseo'santigravityprovider. This PR changes onlyAGENTS.md(5 insertions, 4 deletions), the same five edits as frdminc/tendcf's:paseo run --provider antigravity --model gemini-4-argon --no-wait --title NAME --cwd WORKTREE "$(cat BRIEF)"line (paseo runhas no--prompt-file; the brief ends with the report path, read afterpaseo wait AGENT_ID). The antigravity full-access mode id is to be confirmed before passing--mode.paseo provider models antigravityinstead ofacp-run agy --info.acp-dispatchis a shim overpaseo run, to be replaced bypaseo runlines in a follow-up; every otheracp-dispatchline is unchanged.Opened by the slim-down lead under the operator's J2b grant (2026-11-06).
Generated by Claude Code
Note
Low Risk
Documentation-only refresh; no runtime behavior or security surface touched.
Overview
Updates the standing-rule section of
AGENTS.mdso it reflects djbclark-ade’s 2026-11-06 slim-down: it now statesacp-dispatchis a temporarypaseo runshim and will be swapped for explicitpaseo runinvocations later while keeping existing quota safeguards.It also retargets references from “agy” to Paseo’s antigravity provider—Sonnet slices may use the antigravity Opus pool, Gemini Argon reviews spell out the eventual
acp-dispatch antigravity …command, insist those reviews stay behind--kind frontier(never barepaseo run), and remind reviewers there is still no read-only Google provider, and the weekly Gemini Carbon recheck now runs viapaseo provider models antigravitybecause the agy TUI/acp-run agy --infopath is retired.Reviewed by Cursor Bugbot for commit 3d34a54. Bugbot is set up for automated code reviews on this repo. Configure here.