Repository navigation
feat(kits): add Codex and Antigravity gateway kits - #4
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add independently installable experimental Codex and Google Antigravity (
agy)agent kits consuming acq's neutral configured Chat Completions provider input.
No USAi-specific endpoints, model catalogs or credential values are embedded.
Context and plan
Existing provider kits publish Chat Completions-compatible facts/catalogs.
Neither agent's native wire API matches that contract. Keep adaptation in each
agent kit, preserve exact IDs, scope translation to text/function tools and
reject unsupported behavior. Design records live with each kit.
This branch is based on main and reuses the merged Claude kit's shared validation
and executable-index guard. The PR adds only the two new kits and their shared
test/CI wiring.
Verification transcript
make check PATTERNS=<pinned-checkout> GITLEAKS=<pinned-binary>: PASS.Includes Ruff, formatting, ShellCheck, all six contracts, all offline suites,
28 shared tests, dependency audits, unsafe-shell and secret scanning.
python3 scripts/verify-native-cli.py codex --binary <pinned-arm64-binary>: PASS.Both execute real CLI file tools and verify exact IDs, tool results and final replies.
both catalogs contain only
exact.test_model; both real sessions complete withPASEO_KIT_OK. Final code rerun PASS. Active user daemon was untouched.final review reports no blockers within experimental text/function scope.
These are real CLI/protocol/Paseo tests against synthetic model output, not live
gateway/model-quality verification. Remote CI, native x64 and interactive PTY
remain unverified. Terminal suspension/job control is unsupported.
Security impact
New installation hosts and private loopback services. No published model ports,
persisted keys, disabled TLS verification or global provider config writes.
Upstream redirects are denied; installer redirects checked before following.
Local auth token is separate from outbound correlation metadata. Tool/field
translation uses a limited allowlist. Same-UID guest processes are not isolated.
Paseo's Antigravity plugin uses full access; the kit's terminal wrapper does not
enable that flag. The synthetic file fixture explicitly opts into it.
Limitations
Buffered responses, text/function tools only, no media/native search/encrypted
reasoning/server-side Responses state. Antigravity's fixed automatic thought
envelope is explicitly ignored by the text/function policy; effort flags reject.
CLI state uses kit-owned persistent directories; normal user-global config is
not inherited. Generic Codex catalog instructions may affect model performance.
Rollback
Revert this PR's commits. Remove the two kit references from future sandbox
creation. Existing sandboxes are not modified automatically; do not delete
conversation directories without operator consent.
AI assistance and review
Implementation and verification were AI-assisted. Human review is required;
this is not production approval or a compliance assertion.