Allow API-key auth for remote exec-server registration#24666
Open
sdcoffey wants to merge 2 commits into
Open
Conversation
4e0de11 to
348a07c
Compare
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.
Overview
Allow remote
codex exec-serverregistration to use existing API-key auth for remotes that accept API keys.CodexAuth::ApiKeyfor the normal--remoteregistration path while retaining--use-agent-identity-authas the explicit Agent Identity path.CODEX_API_KEY.Big picture
Callers can now provide an API key directly to
exec-serverregistration without first establishing ChatGPT login state:Validation
cargo fmt --all -- --check(just fmtis not installed on this host)cargo test -p codex-cli -p codex-exec-server(run before the documentation and test-only cleanup; the behavioral code is unchanged)