这是indexloc提供的服务，不要输入任何密码
Skip to content

global endpoint opus4 #4128

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Jun 27, 2025
Merged

global endpoint opus4 #4128

merged 1 commit into from
Jun 27, 2025

Conversation

denisj3030
Copy link
Contributor

REQUIRED: Add a summary of your PR here, typically including why the change is needed and what was changed. Include any design alternatives for discussion purposes.


--- YOUR PR SUMMARY GOES HERE ---


REQUIRED: Fill out the below checklists or remove if irrelevant

  1. If you are opening a PR for Official Notebooks under the notebooks/official folder, follow this mandatory checklist:
  • Use the notebook template as a starting point.
  • Follow the style and grammar rules outlined in the above notebook template.
  • Verify the notebook runs successfully in Colab since the automated tests cannot guarantee this even when it passes.
  • Passes all the required automated checks. You can locally test for formatting and linting with these instructions.
  • You have consulted with a tech writer to see if tech writer review is necessary. If so, the notebook has been reviewed by a tech writer, and they have approved it.
  • This notebook has been added to the CODEOWNERS file under the Official Notebooks section, pointing to the author or the author's team.
  • The Jupyter notebook cleans up any artifacts it has created (datasets, ML models, endpoints, etc) so as not to eat up unnecessary resources.

  1. If you are opening a PR for Community Notebooks under the notebooks/community folder:
  • This notebook has been added to the CODEOWNERS file under the Community Notebooks section, pointing to the author or the author's team.
  • Passes all the required formatting and linting checks. You can locally test with these instructions.

  1. If you are opening a PR for Community Content under the community-content folder:
  • Make sure your main Content Directory Name is descriptive, informative, and includes some of the key products and attributes of your content, so that it is differentiable from other content
  • The main content directory has been added to the CODEOWNERS file under the Community Content section, pointing to the author or the author's team.
  • Passes all the required formatting and linting checks. You can locally test with these instructions.

@denisj3030 denisj3030 requested a review from a team as a code owner June 27, 2025 15:31
@denisj3030 denisj3030 enabled auto-merge June 27, 2025 15:31
gemini-code-assist[bot]
gemini-code-assist bot reviewed Jun 27, 2025
View reviewed changes
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary of Changes

Hello @denisj3030, I'm Gemini Code Assist1! 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 primarily focuses on enabling the use of a global endpoint for the claude-opus-4 model within the anthropic_claude_intro.ipynb sample notebook. Additionally, it includes a small documentation update to guide users towards region information.

Highlights

  • Enable Global Endpoint for Claude Opus: I've updated the anthropic_claude_intro.ipynb notebook to include 'GLOBAL' as an available region for the claude-opus-4@20250514 model. This change allows users to leverage the global endpoint for this specific model, expanding its accessibility.
  • Documentation Clarification: I've made a minor text adjustment in the introductory markdown cell of the anthropic_claude_intro.ipynb notebook. The link referring to the 'Use Claude' documentation now explicitly mentions that it also contains a 'list of supported regions', improving clarity for users.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 is currently in preview and 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 to provide feedback.

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[bot]
gemini-code-assist bot reviewed Jun 27, 2025
View reviewed changes
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

The pull request updates the anthropic_claude_intro.ipynb notebook to include GLOBAL as an available region for the claude-opus-4 model and updates the documentation link to include a list of supported regions. The addition of the GLOBAL region ensures consistency across models and improves usability.

notebooks/official/generative_ai/anthropic_claude_intro.ipynb
Comment on lines 197 to +198
"elif MODEL == \"claude-opus-4@20250514\":\n",
" available_regions = [\"us-east5\", \"europe-west4\"]\n",
" available_regions = [\"us-east5\", \"europe-west4\", \"GLOBAL\"]\n",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

The available regions for claude-opus-4@20250514 should include GLOBAL to be consistent with other models and the documentation update in the first diff. This ensures the model is available in all supported regions, enhancing usability and reducing potential errors for users in different locations.

    available_regions = ["us-east5", "europe-west4", "GLOBAL"]

@denisj3030 denisj3030 added this pull request to the merge queue Jun 27, 2025
Merged via the queue into main with commit 4589293 Jun 27, 2025
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@gemini-code-assist gemini-code-assist[bot] gemini-code-assist[bot] left review comments

@gericdong gericdong gericdong approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@denisj3030 @gericdong