Claude Doing? 0.2.11

• Plan limits: read reliably again. Every open session asked the Claude app for your plan's figures every minute, and with many sessions open the app started answering that it couldn't read them. With companion plugin 0.2.2, sessions share one reading: the app's figures are read at most once every minute and a half in all, and an answer without them never replaces a good one. If the figures can't be read for a while, Usage keeps the last ones for up to an hour, saying how old they are
• Sessions that were already open keep the plugin they started with: restart them, or run /reload-plugins, to use 0.2.2

Claude Doing? 0.2.10

• Daily budget chart: the "Used" line no longer turns into a solid block. Some of the sources of plan readings keep passing on an older weekly figure, and the line zigzagged between them several times a minute. A week's usage only goes up until it resets, so a lower figure from the same week is now left out
• Companion plugin 0.2.1: fixed at the source. Every open Claude session runs the plugin; a session that couldn't read the app's figures passed on its own, which date from its last reply, so idle sessions kept writing old ones. It now passes on another session's recent reading instead, never adds a lower weekly figure for the same week, and no longer briefly replaces the plan with "needs access". The app updates the plugin by itself; sessions use it once they restart

Claude Doing? 0.2.9

• Storage › Projects: project folders with nothing at all in them (only an empty memory folder) are listed under Empty project folders. They were left out because they hold no bytes and no files
• Storage › Projects: projects with nothing left but memories are listed under Only memories left, with Remove all…, or tick them one by one. They're Check first, so never chosen for you, and the clean-up lists every memory that would go and asks you to tick that it's what you want. They go to the Trash, so you can put them back. No other clean-up ever removes memories
• ⌘-Tab: with "Show in the Dock" off, the app joins the Dock and the ⌘-Tab switcher while its main window is open, so you can switch away and back, and leaves both when the window closes. macOS only lists apps in the Dock in ⌘-Tab

Claude Doing? 0.2.8

• Dev containers have their own section under VMs & containers, named after their project: VS Code's Dev Containers (and the devcontainer CLI) by the project folder, DevPod by its workspace. They're marked DC rather than CT, and counted apart on Activity
• Containers: each one is tagged with what runs it: Docker, Podman, Apple, DevPod or Dev Containers
• Claude in dev containers: a dev container's Claude sessions can report to the app. Report sessions… on the container adds a hook to the project's own .claude folder, which the container shares with the Mac: Claude in the container runs it (with Node or Python), and on the Mac it does nothing. Those sessions then show in Activity and Sessions, marked "in dev container", with their live timeline. Nothing in devcontainer.json changes, and Stop Reporting Sessions… (right-click the container) takes it out again. Sessions already running pick it up when they restart. It needs the project folder shared from the Mac, the default for VS Code and for DevPod with a local folder

Claude Doing? 0.2.7

• CPU column: wide enough for the cores line ("0.4 of 16 cores"), which wrapped onto three lines

Claude Doing? 0.2.6

• Hook log: past days' logs are compacted, dropping the plugins' background calls an earlier hook logged: a busy day's log shrinks from around 28 MB to 2 MB. Today's log is left alone while the hook is still writing to it, and is compacted the next day

Claude Doing? 0.2.5

• Starting up: Activity fills in within a few seconds of opening the app. It could stay empty for a minute or more, while the app read every background call the companion plugins make (every few seconds, in every session) from the hook's log
• Hook: those background calls are no longer logged, so the log is a small fraction of its old size. The app brings the hook program up to date when it changes

Claude Doing? 0.2.4

• CPU is now a share of the cores each thing can use, so it never goes over 100%: one of two cores flat out is 50%. A VM and its containers are measured against the VM's cores, everything else against the Mac's, with the cores busy under it ("92%", "7.4 of 8 cores"). It used to be counted as Activity Monitor does, with each core as 100%, so a busy VM could show 725%
• CPU, core by core: rest the pointer on a CPU figure to see each core. A VM shows each of its virtual cores, a container its VM's cores, and anything else the Mac's own cores
• Network: the app reads network use in short readings instead of keeping nettop running, which on its own kept a whole core busy

Claude Doing? 0.2.3

• Storage › Projects: project folders with no chats or memories left in them are listed under Empty project folders, with Remove all… to clear them in one go. They're also on the Overview as Safe. A folder still holding memories is never counted as empty, and Claude Code makes a project's folder again if you go back to it

Claude Doing? 0.2.2

• Updates: the update window opens on top of Settings when you check from there, instead of waiting until Settings closes
• Menu bar and side panel: Check for Updates…, or Install Update when one is waiting. It opens the main window if it's closed