feat(agents-api): add standalone native executor launcher - #593
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
1 participant
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.
Third-party Agents API registries need an executor client that uses service-scoped credentials. This adds the optional, separately named
agents-api-codex-executor, built against pinned Codex 0.153.4 libraries. It reuses native registration, Noise, files, processes, reconnection and shutdown, while the matching stock binary supplies its existing helper modes.The launcher reads an exact-Environment operator credential file, verifies HTTPS certificates/hostnames, keeps private state under
~/.parsar, and does not fall back to OpenAI login or model keys. Its locked Cargo package, independent release build, CI and required checks are separate from the Go API build. All external dependency versions, sources and checksums match the pinned upstream lock.Validation: full
make check; OpenAPI generation without a public-spec change; independent release build and CLI checks; real PostgreSQL/native HTTPS and WSS with untrusted-CA/hostname rejection, file/process/helper/read-only enforcement and connection recovery; real MiniMax through an authenticated daemon with remote commands, cold history/files and cancellation. The executor mount-boundary regression fails with the initial test mount and passes with executor-only state/workspace mounts.Fresh built-in independent full-diff review found no material in-scope issues. The reviewer independently passed the locked checks, copied-context release build and both native/real MiniMax fixtures. Subsequent SSH rejection prevented an independent full
make checkrepeat; the developer’s full gate passed. Evidence is retained on zju_a100_2 under~/.parsar/remediation/20260914/executor-client/and~/.parsar/reviews/executor-client-blind-26ae8810-9bab-42d7-9e0d-a0cbe3fc29f3/.Scope limits: initial Linux x86_64 GNU build with the exact native installation required. TLS acceptance uses controlled DNS and a test CA; the model fixture uses loopback separately. Public
self_hosted, pre-Turn admission, public principal identity, other platforms/release publishing and complete Environment compatibility remain open. Stock CLI domain protection is unchanged; the new command is not stock-command compatibility.