docs: add native macOS companion app to Companion Apps section#222
docs: add native macOS companion app to Companion Apps section#222HAOGRE wants to merge 1 commit into
Conversation
📝 WalkthroughWalkthroughA new "Companion Apps" section is added to ChangesREADME Companion Apps Section
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 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 |
ClaimVerifier: blocking findingsThe following file claims in commit messages / PR body were not actually modified on this branch:
Please update the claim or add the missing changes. |
|
@kramersharp Resolved the ClaimVerifier finding by removing the repository-looking runtime path from the PR body. The branch intentionally only modifies README.md; the v4 state file is consumed at runtime by the companion app and is not part of this PR diff. |
Preview
Status Bar
Dark Mode
Light Mode
Summary
Following up on the feedback from #215 — as suggested, I've built a separate companion repository that consumes the v4 state protocol instead of being merged into the core package.
This PR adds a small Companion Apps section to the README listing the macOS menu bar app.
What was built
Claude Token Monitor for macOS
A native Swift/SwiftUI menu bar app that:
~/.claude/projects/*.jsonldirectly for token stats and cost trackingThis strictly follows the companion-app architecture you outlined: the Python project owns the data/protocol layer, the macOS app is a pure consumer.
Change
Single addition to README.md: a 🛠️ Companion Apps section before Star History, with one table row linking to the macOS app.
Happy to adjust the wording, placement, or table format to fit your style.
🤖 Generated with Claude Code
Summary by CodeRabbit