Add file-based API key support for server mode#36
Merged
Conversation
caol64
approved these changes
Jul 12, 2026
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
2 participants
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
serve --api-key-file <path>for file-mounted secrets--api-keyWhy
Passing an API key with
--api-keyexposes the secret in the process command line. File-based loading allows Docker and other secret mounts to keep it out of argv while preserving the existing option for compatibility.Compatibility
Existing
--api-keybehavior and unauthenticated server mode remain unchanged.Test plan
pnpm test(37/37)pnpm typecheckpnpm buildpnpm exec eslint .(no errors; two pre-existing warnings)