Conversation
|
|
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (5)
📒 Files selected for processing (1)
📝 WalkthroughSummary by CodeRabbit
WalkthroughUpdated documentation for Claude Code authentication configuration, clarifying that an API key remains required when using a custom Bifrost base URL. Modified OAuth setup sections to replace Bifrost URL configuration steps with explicit environment variable guidance, and added precedence notes for API key handling in custom authentication scenarios. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes Poem
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Merge activity
|
🧪 Test Suite AvailableThis PR can be tested by a repository admin. |
Confidence Score: 5/5Pure documentation fix — no code changes, safe to merge All changes are documentation-only. The clarifications are accurate and consistent with the existing API key behavior described in the codebase. The only finding is a very minor comment-wording suggestion (P2). The new GWS images follow the established pattern in the docs/media/user-provisioning/ directory. No files require special attention Important Files Changed
Reviews (1): Last reviewed commit: "docs fixes" | Re-trigger Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| 1. **Set environment variables** | ||
| ```bash | ||
| export ANTHROPIC_API_KEY=your-bifrost-virtual-key # or "dummy" if virtual keys are not enabled | ||
| export ANTHROPIC_AUTH_TOKEN=your-bifrost-virtual-key # same value |
There was a problem hiding this comment.
# same value comment could be clearer
The comment # same value on the ANTHROPIC_AUTH_TOKEN line implicitly refers to the value on the ANTHROPIC_API_KEY line above, but doesn't remind the reader that "dummy" is also valid here when virtual keys are not enabled. A user who sets ANTHROPIC_AUTH_TOKEN without reading the previous line carefully might miss that nuance.
Consider making the comment more self-contained, e.g. # same value as ANTHROPIC_API_KEY (or "dummy"). The same applies at line 51 in the Teams/Enterprise section.
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
2 participants
Summary
Updates Claude Code documentation to clarify that API keys are always required when using custom base URLs like Bifrost, even for OAuth-based authentication methods. Adds new images for Google Workspace user provisioning setup.
Changes
ANTHROPIC_API_KEYis required when routing through custom base URLs, even for Pro/Max/Teams accounts using OAuthANTHROPIC_AUTH_TOKENenvironment variable setup alongsideANTHROPIC_API_KEYin configuration examplesANTHROPIC_API_KEYis always required with custom base URLsType of change
Affected areas
How to test
Verify the documentation renders correctly and the new environment variable examples work as expected:
The new environment variables
ANTHROPIC_API_KEYandANTHROPIC_AUTH_TOKENare now documented as required when using custom base URLs, even for OAuth authentication flows.Screenshots/Recordings
Added new images for Google Workspace setup:
gws-auth-client-creation.pnggws-connection-status.pnggws-domain-wide-delegation.pnggws-service-account-id.pnggws-service-key-creation.pngBreaking changes
Related issues
Security considerations
The documentation now properly emphasizes that API keys are required for custom base URL configurations, ensuring users understand the authentication requirements for secure Bifrost integration.
Checklist
docs/contributing/README.mdand followed the guidelines