Fix: Use x-api-key header for Claude API instead of Authorization: Bearer

[dacsang97]

Problem

The Claude executor was using Authorization: Bearer <api-key> header format, which causes 401 authentication errors when using custom proxy endpoints that expect the standard Anthropic x-api-key header format.

Root Cause

Anthropic's API documentation specifies using x-api-key header for authentication, not Authorization: Bearer. While the official Anthropic API may accept both formats, custom proxy endpoints often require the standard x-api-key header.
https://platform.claude.com/docs/en/get-started

Solution

Modified applyClaudeHeaders() function in internal/runtime/executor/claude_executor.go to use:

r.Header.Set("x-api-key", apiKey)

instead of:

r.Header.Set("Authorization", "Bearer "+apiKey)

Changes

• Updated authentication header format for Claude API requests

Impact

• Maintains compatibility with standard Anthropic API authentication

Testing

Tested with:

• Standard Claude API endpoints
• Custom headers from configuration are still applied correctly

[gemini-code-assist]

Summary of Changes

Hello @dacsang97, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses an authentication incompatibility issue with the Claude API when interacting with custom proxy endpoints. By aligning the API key header format with Anthropic's official specification, the change ensures reliable authentication across various deployment scenarios, improving the robustness of Claude API integrations.

Highlights

• Claude API Authentication Fix: Resolved 401 authentication errors when using custom proxy endpoints for the Claude API by switching from the Authorization: Bearer header to the standard x-api-key header format, as specified by Anthropic.
• Header Format Alignment: The applyClaudeHeaders() function in internal/runtime/executor/claude_executor.go was updated to correctly set the x-api-key header, ensuring compatibility with official Anthropic API documentation and custom proxy expectations.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request aims to fix an authentication issue with the Claude executor by changing the authentication header from Authorization: Bearer to x-api-key. This aligns with Anthropic's API documentation for static API keys.

While the change is correct for static API keys, I've identified a potential regression that could break authentication for users relying on OAuth access tokens. The executor can use both static keys and OAuth tokens, but the proposed change uses x-api-key for both. I've provided a critical-severity comment with a code suggestion to handle both authentication methods correctly by dynamically choosing the appropriate header based on the credential type.