sync: port upstream CLAUDE_CONFIG_DIR for Claude instances (#4017) - #160
Conversation
|
@coderabbitai review |
✅ Action performedReview finished.
|
|
Warning Review limit reached
Next review available in: 36 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (6)
📝 WalkthroughWalkthroughChangesClaude configuration directory
Estimated code review effort: 2 (Simple) | ~10 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ca317a0d40
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
…IG_DIR Persisted homePath values historically meant a HOME override (Claude used $HOME/.claude). Map those to CLAUDE_CONFIG_DIR via resolveClaudeConfigDir, and key continuation/cache by the effective config directory including the default ~/.claude.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ea93c8fbfb
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| if (path.basename(resolvedHomePath) === ".claude") { | ||
| return resolvedHomePath; | ||
| } | ||
| // Legacy HOME override layout: config lived under `$HOME/.claude`. | ||
| return path.join(resolvedHomePath, ".claude"); |
There was a problem hiding this comment.
Honor arbitrary CLAUDE_CONFIG_DIR paths
When a user follows the newly relabeled CLAUDE_CONFIG_DIR path setting in packages/contracts/src/settings.ts and enters a valid custom directory such as ~/.claude-work, this basename heuristic silently exports ~/.claude-work/.claude instead of the requested path. Claude then loads a different, typically empty configuration and can appear logged out or lose access to that instance's settings. Legacy HOME values need an explicit migration/version distinction rather than treating every path not literally named .claude as a legacy home.
Useful? React with 👍 / 👎.
Merge activity
|
…ngdotgg#4079) (#161) ## What changed - Ports upstream `pingdotgg#4079`: attach live thread event buffer before snapshot/catch-up reads so events published during load are not dropped. - Preserves fork: full-range `afterSequence` HTTP catch-up replay and per-thread filters already present on fork `ws.ts`. ## Validation - New server test for snapshot buffering passed in port worktree - Tip stack: `vp check` and `vp run typecheck` passed Stack: 2 of 6; depends on #160.

What changed
#4017: useCLAUDE_CONFIG_DIRinstead of overridingHOMEwhen isolating Claude instance config, so macOS keychain OAuth still works.homePathkey retained).Validation
CLAUDE_CONFIG_DIR) tests passed in port worktreevp checkandvp run typecheckpassedStack: 1 of 6; base
main.Summary by CodeRabbit
Bug Fixes
HOMEenvironment variable, improving compatibility with macOS keychain access.Documentation