8000 fix: keep Gemini API keys out of request URLs by simon-inkie · Pull Request #5 · simon-inkie/inkie-auto-mode · GitHub
[go: up one dir, main page]

Skip to content

fix: keep Gemini API keys out of request URLs - #5

Merged
simon-inkie merged 2 commits into
masterfrom
simon/ink-927-move-gemini-adapter-api-keys-from-query-urls-to-headers
Sep 21, 2026
Merged

simon-inkie merged 2 commits into
masterfrom
simon/ink-927-move-gemini-adapter-api-keys-from-query-urls-to-headers

Conversation

@simon-inkie
Copy link
Copy Markdown
Owner

Summary

  • moves Gemini credentials to x-goog-api-key in Cursor, Claude Code and OpenClaw adapters
  • removes API-key query transport from all three generateContent URLs
  • adds dynamic URL/header assertions, including OpenClaw runtime-auth coverage

Closes INK-927.

Verification

  • npm test 380/380
  • npm run typecheck
  • npm run build
  • git diff --check
  • Andor PASS on 2d89fc5, including 18/18 mutation checks
  • Aggy PASS on 2d89fc5

Boundary

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.

@simon-inkie
simon-inkie merged commit f17615b into master Sep 21, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

0