Repository navigation
fix: keep Gemini API keys out of request URLs - #5
Merged
simon-inkie merged 2 commits intoSep 21, 2026
Merged
simon-inkie merged 2 commits into
simon-inkie merged 2 commits into
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
x-goog-api-keyin Cursor, Claude Code and OpenClaw adaptersgenerateContentURLsCloses INK-927.
Verification
npm test380/380npm run typechecknpm run buildgit diff --check2d89fc5, including 18/18 mutation checks2d89fc5Boundary
No live Gemini call, benchmark change, secret, runtime-config change, or deployment is included. Header acceptance against the live provider remains intentionally deferred pending an approved non-secret verification route.