Nothing to grant
The first launch asks for nothing: no Full Disk Access, no keychain dialog, no prompt of any kind.
Sissy is the menu bar companion for developers. Everything is read from what is already on your Mac and the services you connect.
macOS 26 or later·
The cost is what Sissy counted at published rates, not what a vendor charged.
Try it: click an account or any tab.
Limits
The Usage tab shows one gauge per account, on the window it is closest to running out of. The Forge tab reads GitHub Actions minutes on the same gauge.
69%
The mark on the bar is where even spending would have reached by now, so being ahead of pace is visible instead of calculated.
Claude · xSmyile · weekly windowPace at this hour
user scope on a classic token; an organisation's need only repo, where you own it or manage its billing.Accounts
A work account, a personal one, a Codex sign-in beside them: each gets its own row, its own windows and its own plan. The day's cost adds them up. The limits never do, because a window belongs to an account.
CLAUDE_CONFIG_DIR off the process and counts the sessions on each account. The picker changes what you read and nothing else. Claude Code stays on the account it is signed into.Agents
A rate limit and the Mac's memory are the two things that stop work now, so the sessions have a tab of their own beside the gauges, and the Mac has the next one.
Keep awake
The cup in the panel header holds the Mac awake while agents are working, letting go ten minutes after they stop, or always, for eight hours by default, anything from one hour to twelve, or no limit at all. The cup's menu and Settings' Awake tab carry the same switches.
Git
The work repository you are about to push under your personal name, or the other way round. For every repository your agents have worked in, Sissy asks git who would sign the next commit, and compares it with the other repositories on the same forge account.
Findings come first, with the name it would commit under, what its forge expects and how many repositories say so, and the file the wrong value comes from. Where that file is the repository's own, Copy the fix puts the git config --unset-all command on the clipboard. Sissy never writes to a repository or to any git config. A commit made with -c, --author or GIT_AUTHOR_EMAIL is outside what it can see, and the page says so.
gh or glab already holds, or one you paste. Every counter has a switch there, and one switched off is not asked for.Disk and network
The Disk and Network tabs sit beside the Mac's, and like it they read the machine itself: nothing to grant, and nothing asked of anyone.
Privacy
Sissy reads the logs Claude Code and Codex already write on your Mac and does the arithmetic there. It has no account of its own, no analytics and no crash reporting, and it binds no port.
The first launch asks for nothing: no Full Disk Access, no keychain dialog, no prompt of any kind.
Sissy does connect out, for readings you asked for: each vendor's usage endpoint, the public price list, a forge you connected, a status page, its own update feed. Each has an off switch of its own, the way the counters above do. The two requests that are not readings, spending a Codex reset and spending a Claude one, each wait for you to press and confirm.
Anything that costs a permission, writes into another program's files, or keeps the Mac working with its lid closed is off until you switch it on, and says what it will do first.
| Host | For | Off |
|---|---|---|
raw.githubusercontent.com | LiteLLM's public price list, daily | remotePricing: false |
api.anthropic.com | Usage and profile, with Claude Code's own token, and a reset you confirm spending | Switch the Claude Code provider off |
claude.ai | Usage and credits for a Claude account you linked | Unlink the account |
chatgpt.com | The Codex usage endpoint, and a reset you confirm spending | Switch the Codex provider off, or unlink |
auth.openai.com | Signing a Codex account in, and renewing that credential afterwards | Unlink the account |
api.github.com, or the Enterprise or GitLab host you connected | Your own activity counts, and on github.com your Actions minutes | Disconnect it in Settings › Forge |
status.claude.com, status.openai.com | Each vendor's public status page | statusChecks: false |
sissy.smyile.com | The update feed, daily | Settings › About › Check for updates automatically |
github.com | Downloading an update you, or Install updates automatically, accepted | Decline the update |
One day-by-model archive under ~/Library/Application Support/Sissy/history/: totals, repository paths, session counts and how long each day was worked. Never prompts, and never a line of your logs. Settings names the folder, deletes it on a button, and historyRetentionDays bounds it, with 0 recording nothing.
Off by default. Name projects even when Sissy is off adds one line to ~/.claude/settings.json and one to ~/.codex/hooks.json, and takes both out when you switch it off.
How it works
No daemon, no socket, no second half to keep in step. Quit Sissy and the counting stops.
ccusage prices from LiteLLM too, which is why the two agree.~/.claude/projects/**/*.jsonl, or wherever claudeDataDir points~/.codex/sessions/**/rollout-*.jsonl, honoring CODEX_HOMEgit, to resolve a project and read its commit identityBoth CLIs report the same things: tokens, cost, the per-repository split, the sessions and agents behind them, every rate-limit window, the plan and the credits. Claude Code is on unless you switch it off; Codex is picked up whenever its session directory exists.
Install
macOS 26 or later, Apple Silicon or Intel. Free and open source.
brew install --cask xsmyile/sissy/sissyThe app is Developer ID signed and notarized, so there is no xattr workaround and no right-click › Open. The first launch asks for nothing, and from then on Sissy updates itself: it checks once a day and asks before installing.
brew uninstall --cask sissyOr drag Sissy out of Applications. Either way the counting stops: no daemon to kill, no power assertion still held, nothing listening anywhere.