Your agents, your Mac, your repos. One click away.

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·Apple Silicon or Intel·No account, no telemetry

The cost is what Sissy counted at published rates, not what a vendor charged.

Try it: click an account or any tab.

See the numbers

Limits

See how close you are before the CLI, or CI, stops you.

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

Session and week Click the gauge for that account's own page: the session and the week, each with what is used, how far off pace it is, when it runs out at this rate and when it resets.
Resets A Codex or Claude Code page also counts the resets the vendor gave the account, and spends one on a press you confirm, saying first when the window would reset on its own and whether the vendor counts one as needed yet. Claude Code's are spent with the CLI's own sign-in, so only on the account it is signed in to.
Actions minutes How much of each monthly GitHub Actions allowance your private repositories spent, and which repository and runner spent the most. Where the plan stops CI at the allowance, the row says until when. Your own minutes need the user scope on a classic token; an organisation's need only repo, where you own it or manage its billing.

Accounts

Several accounts, each metered on its own.

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.

One page each
The picker at the top of a page moves between that vendor's accounts. Each goes by its owner or its team, with the plan beside the name, because it is the account that is on a plan and not the CLI. Settings picks the format, and renames any one of them.
In use
A running Claude Code's account comes from its own config file: Sissy reads 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.
Link another
Sissy reads the account each CLI is signed into for free. Linking another signs in once, in a window of its own, and reads its limits beside it. Your terminal stays on the account it is on.

Agents

What is running right now, and what it holds.

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.

Sessions Every running session with its memory, its CPU and how long it has been up, named after the repository it is working in. The same tab counts the period: sessions, sub-agents, how long it was worked and what the cache answered.
Mac Memory pressure as the kernel grades it, swap, load and uptime, and the apps holding the most besides the sessions.

Keep awake

Close the lid. The agents keep working.

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.

The lid
On a MacBook, Keep working with the lid closed keeps a held Mac working with its lid shut, on battery too, down to a floor you pick: 15% unless you change it. Below it a closed Mac sleeps, and the lid sleeps it as usual until it is back on power. It is off until you switch it on, and the first time it says what that costs before it does.
The screen
Keep the screen on too is the other half. Off lets the display sleep and lock while the Mac stays awake underneath for the agents.
Nothing to undo
The hold dies with Sissy: quit and the Mac sleeps normally, lid included. After a crash the lid stays ignored until Sissy is opened again or the Mac restarts.

Git

Catch the wrong name before you push.

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.

By project Where the day went, one row per repository. A worktree counts against the one it was cut from, whichever CLI did the work. Pick a span of days on the panel's calendar and the rows follow it.
Contributions What you pushed on each forge you connected, and under the figures the last thing you pushed, opened, merged or commented on. Settings › Forge connects GitHub, GitHub Enterprise or GitLab with a token 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

Room on the disk, and what the link carries.

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.

Disk Free space graded against the Mac's RAM, marked where it turns warn and critical, read and write activity, and every other local volume.
Network What the links carry now and over the last two minutes, what they carried since boot, and the Wi-Fi signal.

Privacy

Your session logs never leave the machine.

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.

Nothing to grant

The first launch asks for nothing: no Full Disk Access, no keychain dialog, no prompt of any kind.

Every request has a switch

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.

Off until you say so

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.

Every host Sissy talks to, and how to switch each one off
HostForOff
raw.githubusercontent.comLiteLLM's public price list, dailyremotePricing: false
api.anthropic.comUsage and profile, with Claude Code's own token, and a reset you confirm spendingSwitch the Claude Code provider off
claude.aiUsage and credits for a Claude account you linkedUnlink the account
chatgpt.comThe Codex usage endpoint, and a reset you confirm spendingSwitch the Codex provider off, or unlink
auth.openai.comSigning a Codex account in, and renewing that credential afterwardsUnlink the account
api.github.com, or the Enterprise or GitLab host you connectedYour own activity counts, and on github.com your Actions minutesDisconnect it in Settings › Forge
status.claude.com, status.openai.comEach vendor's public status pagestatusChecks: false
sissy.smyile.comThe update feed, dailySettings › About › Check for updates automatically
github.comDownloading an update you, or Install updates automatically, acceptedDecline the update

What Sissy keeps

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.

What it writes elsewhere

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.

SECURITY.md has the full surface: what Sissy reads, runs and holds ›

How it works

One process, reading the logs as they land.

No daemon, no socket, no second half to keep in step. Quit Sissy and the counting stops.

Priced as it lands
Sissy watches the log directories and prices each turn as it lands. The readings that are not a log tail, such as limits, forge counters and vendor status, are polls beside it.
Picks up where it left off
Counting happens while Sissy runs and resumes where it stopped, so Start at login is what keeps a day complete.
No price table in the source
Rates come from LiteLLM at runtime, with a snapshot compiled in as the offline floor, so a CLI that ships a new model prices correctly without a Sissy release. ccusage prices from LiteLLM too, which is why the two agree.
What it reads, and where
Claude Code
~/.claude/projects/**/*.jsonl, or wherever claudeDataDir points
Codex
~/.codex/sessions/**/rollout-*.jsonl, honoring CODEX_HOME
GitHub, GitLab
Each vendor's API, with a token you connect in Settings › Forge
Your repositories
git, to resolve a project and read its commit identity

Both 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

Put Sissy in the menu bar.

macOS 26 or later, Apple Silicon or Intel. Free and open source.

Download for macOS$brew install --cask xsmyile/sissy/sissy

The 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.

Source on GitHub ›
Uninstall
$brew uninstall --cask sissy

Or drag Sissy out of Applications. Either way the counting stops: no daemon to kill, no power assertion still held, nothing listening anywhere.