Add support for OAuth model aliases for Claude

[mcowger]

Introduce support for model aliases in the configuration for Claude OAuth accounts, allowing users to reference models with shorter names. This enhances the API request process by simplifying model name usage.

[gemini-code-assist]

Summary of Changes

Hello @mcowger, 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 streamlines the process of interacting with Claude models via OAuth by introducing a model aliasing feature. Users can now configure shorter, more memorable names for Claude models, which the system will automatically translate to their full upstream identifiers. This change simplifies API request construction and improves usability for authenticated Claude accounts without altering the underlying model functionality.

Highlights

• Configuration for Claude OAuth Model Aliases: Introduced a new configuration section in config.example.yaml and a corresponding field in internal/config/config.go to allow users to define custom aliases for Claude models when using OAuth authentication.
• Model Alias Resolution Logic: Implemented logic within internal/runtime/executor/claude_executor.go to resolve these defined aliases to their actual upstream model names during API requests, specifically for Claude OAuth accounts.
• Dynamic Model Registration: Enhanced sdk/cliproxy/service.go to dynamically register these Claude OAuth model aliases, making them available for use within the system.

🧠 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 introduces support for model aliases for Claude OAuth accounts, which is a great enhancement for usability. The implementation is logical and covers both model resolution during requests and model listing. I've identified a couple of areas with opportunities for performance improvement by centralizing the normalization of alias configurations. Overall, a solid contribution.

[hkfires]

This feature already exists.

[mcowger]

This feature already exists.

For Claude code (not Claude API, where it does exist)? I can't find it.

Can you point me to it?

[hkfires]

This feature already exists.

For Claude code (not Claude API, where it does exist)? I can't find it.

Can you point me to it?

Sorry, I misread that. For aliases, we will have a global consideration, not limited to OAuth from Claude.

[mcowger]

That would be great - I assumed that was not desired due to how it's implemented elsewhere on a per API basis

[mcowger]

Closing this in favor of this suggestion based on feedback from @hkfires

#716