Add Headroom — Claude Code usage monitor for macOS menu bar

[patwalls]

What

Adds Headroom to content/tools/headroom.mdx.

Why

Headroom is a native macOS menu bar app that shows Claude Code's 5-hour session and 7-day weekly utilization as a live percentage, color-coded (calm → amber → red) as limits approach.

Architecture: Instead of polling the Anthropic API, it reads the local file Claude Code's own statusline hook writes to ~/.claude/headroom-usage.json. Zero network calls, zero config — install and the number is there.

• Free, MIT, signed & notarized by Apple
• Download: https://headroom.walls.sh or brew install --cask patwalls/tap/headroom
• ~780 lines of AppKit Swift, no dependencies

🤖 Generated with Claude Code

[coderabbitai]

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)

• content/tools/headroom.mdx is excluded by !content/**

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 00f0875c-69d7-47a4-a6b1-77a62cafe430

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gittensory]

Important

Gittensory found maintainer review notes

Public GitHub metadata was checked for review readiness. Gittensor-specific context appears only when confirmed.

Readiness score: 80/100

Signal	Result	Evidence	Action
Linked issue	⚠️ Missing	No linked issue or no-issue rationale found.	Explain no-issue PR.
Related work	✅ No active overlap found	No same-issue or scoped active PR overlap found.	No action.
Review load	✅ 20/20	Readiness component derived from cached public PR metadata and labels; size label size:M.	No action.
Validation evidence	⚠️ 12/25	Cached preflight status needs author follow-up.	Add validation note.
Open PR queue	✅ 10/10	0 open PR(s), 0 likely reviewable.	No action.
Contributor context	❌ No public Gittensor match	patwalls; not a blocker.	No action.
Gate result	✅ Passing	No configured blocker found.	No action.

Signal definitions

• Related work = same linked issue, overlapping active PRs, or title/path similarity.
• Review load = cached public PR metadata such as size labels, changed paths, and preflight status.
• Open PR queue = repo-wide review pressure; it is not a PR quality failure.
• Contributor context = public GitHub/Gittensor identity context; non-Gittensor status is not a blocker.

Review context

• Author: patwalls
• Role context: outside_contributor
• Public audience mode: oss maintainer
• Lane context: Repository is configured for direct PR review.
• Public profile languages: not available
• Contributor context: Public profile only; not a blocker.
• PR-specific overlap: none found.

Maintainer notes

• No linked issue detected: The planned PR does not reference a closing issue or explicit linked issue number.

Contributor next steps

• Explain no-issue PR.
• Add validation note.
• Link the issue being solved, or explicitly explain why this is a no-issue PR.

• Re-run Gittensory review

---

Checked by Gittensory, a quiet PR intelligence layer for OSS maintainers.

[reviewwed]

Warning

🔧 Almost there — a required check is failing

Thanks for the submission! It's in scope, but a required check didn't pass, so it can't be merged yet.
This PR is left open — fix the issue and push to your branch, and the maintainer review will continue automatically.

Failing checks

• required-pr-gate

Open the Checks tab above to see the exact problem. The most common ones are a missing field (e.g. documentationUrl)
or a source URL that isn't reachable. Once the checks go green, this review re-runs and your entry is evaluated for merge.

Category: tools · Automated by the HeyClaude maintainer agent.

[superagent-security]

Superagent didn't find any vulnerabilities or security issues in this PR.

[JSONbored]

Hi @patwalls - can you please add a proper documentationUrl field to this? Thanks 🙌🏻