Skip to content

fix: no Documents-folder prompt (path-based worktree rollup)#12

Merged
Balanced02 merged 1 commit into
mainfrom
fix/no-documents-access
Jul 13, 2026
Merged

fix: no Documents-folder prompt (path-based worktree rollup)#12
Balanced02 merged 1 commit into
mainfrom
fix/no-documents-access

Conversation

@Balanced02

Copy link
Copy Markdown
Owner

The worktree→project rollup read the .git file at each project's working dir (under ~/Documents), triggering a macOS privacy prompt. Now derives project names from the path string alone — no filesystem access outside ~/.claude, ~/.codex, ~/.gemini, and Application Support.

…rompt)

The worktree→project rollup called gitMainRepo(), which stat/read the .git
file at each Claude project's working directory. Those dirs live under
~/Documents, so macOS fired an "access your Documents folder" prompt — which
a menu-bar usage app has no reason to trigger and looks suspicious.

Derive the project name from the cwd string alone (the .claude/worktrees/
path markers already collapse the user's worktrees correctly, no filesystem
access). Removed gitMainRepo + its test; cost-cache signature bumped to v4.
The app now touches only ~/.claude, ~/.codex, ~/.gemini and its own
Application Support store.
@coderabbitai

coderabbitai Bot commented Jul 13, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@Balanced02, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 6 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 504ffe4e-bee0-4fd9-82b8-9bdf057c4c9f

📥 Commits

Reviewing files that changed from the base of the PR and between 49b2d9a and 4399504.

📒 Files selected for processing (3)
  • CHANGELOG.md
  • Sources/AIUsageBarCore/Claude/ClaudeCostReader.swift
  • Tests/AIUsageBarCoreTests/CoreTests.swift
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/no-documents-access

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@Balanced02
Balanced02 merged commit 3fb5859 into main Jul 13, 2026
2 checks passed
@Balanced02
Balanced02 deleted the fix/no-documents-access branch July 13, 2026 13:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant