Sissy 0.2.3

v0.2.3: What the agents are doing, and what the cache did for them

• The agents page leads with its counts, so the window picker stays put
  while agents start and exit. The running list folds past five, with what
  the rest are holding.
• The Overview's way into the agents page now sits on the providers label.
• Each running agent shows its CPU load, and the page says how much CPU
  time and energy the agents have used since Sissy started counting.
• The memory chart stacks the hour by agent, and every row has its own CPU
  lane on the same time axis.
• A new Under the hood section follows the page's window: how much of your
  input the prompt cache answered, what that saved at list price, and the
  longest turn.
• After updating, Sissy reads the CLIs' logs once more in the background to
  fill in the longest turn for the days it already archived.

Sissy 0.2.2

v0.2.2: A calmer panel and a refresh that says so

• The commit identity page leads with a recap: whether anything is wrong,
  how many repositories agree, and which one you opened it for. Only the
  repositories with a problem are listed above the fold.
• Expanding or collapsing that list keeps the control under the pointer.
• The Overview's commit identity line is there every day, and says when
  nothing has been read yet instead of claiming everything agrees.
• The fix Sissy copies for a repository now unsets only the keys that
  repository sets itself, including a key it sets twice.
• The identities and agents pages show when they were last read, and
  "checking…" or "counting…" while a refresh runs.
• Right-click the menu bar icon and choose Refresh All (⌘R) to re-read
  every provider, forge, repository and agent at once.
• Project lists fold at three rows, and the effort breakdown moved behind
  one row on each provider's page.
• Linking an account is sturdier: the login window's Cancel and Retry
  behave as cancels, and a stale result from a closed window is ignored.

Sissy 0.2.1

Linked accounts that name themselves, and a way back from the keychain

• Accounts linked in Settings now show their name as soon as Sissy learns it,
  not a raw id until the next launch.
• A credential Sissy cannot read shows an Allow button right on its row in
  Settings, for forge connections and linked Claude and Codex accounts alike.
  It used to be reachable only from a secondary click in the panel.
• Development builds keep their credentials apart from the released app's.

Sissy 0.2.0

The numbers you keep checking, in the menu bar

What your coding agents cost, how close you are to a rate limit, where the work
went, what the sessions running now are holding, and what you pushed: all read
from the logs already on your Mac and the services you connect. No account of
its own, no telemetry, nothing to grant at first launch.

The panel

• An Overview, and a page per provider behind it.
• A rate-limit gauge on every account, on whichever window your current pace
  empties first. The mark on the bar is where even consumption would have
  reached by now, so running hot is visible instead of calculated.
• A period on the headline: Today, 7 days, 30 days or All.
• Where the day went, by repository. A worktree counts against the repository
  it was cut from, so one project stays one row.
• The day's split by model, as pills under the strip, answering for whichever
  day the pointer is on.
• An agents page: what the CLIs on this Mac are holding right now, how long the
  day has been worked, and how much of it went to sub-agents.
• At what effort each model was worked.

Accounts

• Link a Claude account by signing in to claude.ai, in a window Sissy opens once
  and closes when the link is done.
• Hold a credential per Codex account and read every one of them.
• Switch which account Claude Code starts as, after saying what that undoes.
• Every account gets its own row, its own name and its own limits.

Limits

• Read per account from the CLI's own credential. No keychain dialog, no cookie
  to paste, nothing to grant.
• Codex answers from the vendor rather than waiting for its next turn.
• When a reading is missing the row says why, including a vendor's 429, and
  offers the click that gets it back.

Forges

• Connect GitHub or GitLab with a token you hand over, and see what each account
  contributed, opened and commented over the period you picked.
• Each counter has a switch, and one switched off is never fetched.
• A repository committing under a name its forge does not expect is flagged.

Keeping the Mac up

• Hold the Mac awake while the agents are working, with the display free to
  sleep on its own schedule.

History

• A day-by-model record of every day Sissy metered, filled in once from what the
  CLIs had already logged, so a wide period is honest on a fresh install.
• Export it as CSV.

Also

• Sissy can start at login.
• Settings has a tab per concern: General, Providers, Forge, About.
• Each vendor's own status page is read, so a CLI that has started failing can
  be told apart from a vendor that has.
• About carries a diagnostics report, for when you file a bug.

Gone

• The ESP32 companion and the firmware behind it. The last state where it built
  and paired is the companion branch.
• The mood pop-up and the milestone celebrations. They rode the cost axis, which
  says nothing to anyone whose daily spend sits far from a threshold. What leads
  the panel now is rate-limit pressure, on each account's own row, which reads
  the same for everyone.

Requires macOS 26. Signed and notarized, so there is no right-click to open.

Sissy 0.1.8

What's Changed

• feat(build): derive app version from the git tag by @xsmyile in #20

Full Changelog: v0.1.7...v0.1.8

Sissy 0.1.7

Full Changelog: v0.1.6...v0.1.7

Sissy 0.1.6

Full Changelog: v0.1.5...v0.1.6

Sissy 0.1.5

What's Changed

• Pricing-drift monitor + rate Claude 5 and gpt-5.x models by @xsmyile in #19

Full Changelog: v0.1.4...v0.1.5

Sissy 0.1.4

What's Changed

• fix(daemon): split Claude cache_creation into 5m/1h pricing tiers (v0.1.4) by @xsmyile in #18

Full Changelog: v0.1.3...v0.1.4

Sissy 0.1.3

What's Changed

• Cleanup sweep: WS hardening, dead-code removal, dedup (v0.1.3) by @xsmyile in #17

Full Changelog: v0.1.2...v0.1.3