fix: detect Anthropic auth token from process environment#644
fix: detect Anthropic auth token from process environment#644michaeledi wants to merge 1 commit intositeboon:mainfrom
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughUpdated Claude credential authentication to prioritize the Changes
Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
Why PR #527 did not fully fix this
PR #527 added support for ANTHROPIC_API_KEY and ANTHROPIC_AUTH_TOKEN when they are stored under ~/.claude/settings.json env values. That helps setups where Claude Code reads proxy/auth values from settings.json, but it does not cover local service managers such as systemd, pm2, Docker, or shell-launched processes that inject ANTHROPIC_AUTH_TOKEN directly into the CloudCLI server process environment.
In those deployments, Claude/SDK execution can receive ANTHROPIC_AUTH_TOKEN from process.env and work correctly, while the CloudCLI status endpoint still reports disconnected because it only checked process.env.ANTHROPIC_API_KEY before falling back to settings.json and OAuth credentials.
Validation
Summary by CodeRabbit