What is Claude doing?
Every Claude Code session, what it’s doing right now, and everything it has started: the dev servers, containers and whole virtual machines. Spot what’s been left running, see your plan usage, and tidy up the disk space Claude uses. Use OpenAI’s Codex too? Turn on the Codex beta and see both side by side.
Free · macOS 26 or later · For the Claude Code CLI and the Claude desktop app, and Codex in beta · Signed and notarised by Apple
Everything your AI agents are up to, in one place
Claude Code and Codex run a lot on your Mac: a process for every session, shells, servers and tools below them, and, through Docker or Parallels, containers and VMs that Activity Monitor files under those apps instead. Claude Doing? puts it all back together.
Every session, live
Every Claude Code session, from the terminal, an IDE or the desktop app (and every Codex session, with the beta on), each listed once, working, waiting for you or idle, with what it's doing right now, its CPU and memory, and a timeline of every command, edit and search it made.
What each session started
Dev servers, MCP servers, Docker and Podman containers, dev containers (VS Code and DevPod), Parallels, UTM, VMware, VirtualBox, Lima, Multipass, Tart and OrbStack VMs, each linked to the session that started it, with a Stop or Suspend button.
What's been left running
When a session closes, whatever it started can keep running. Claude Doing? flags it, tells you once, and stops it all with one click when you're ready.
The whole Mac
CPU core by core, memory with macOS's memory pressure and swap, network, disk, GPU and the busiest processes, for everything running, not just your AI agents, with charts that look back up to seven days.
Plan usage and a daily budget
Your 5-hour and weekly limits (and per-model limits with the Claude desktop app), a daily budget that rolls a quiet day's spare over the days left, tokens by hour, day, project and model, an estimate of use from outside Claude Code on this Mac, and alerts. With the Codex beta, the same for your Codex plan.
Storage, tidied safely
The gigabytes of caches, chat histories, screenshots and old versions Claude and Codex leave on disk, each marked Safe, Check first, Keep or In use, with clean-up to the Trash and undo.
Codex too, side by side with Claude
If you use OpenAI’s Codex as well, through the Codex app, its command-line tool or VS Code, turn on the Codex beta when the app asks, or later in Settings. Claude and Codex each get their own Sessions and Usage in the sidebar, and every other page shows both.
Its sessions and what they start
Your open and recent Codex sessions, what each is doing, its tokens, and the containers and processes it started, marked Codex owned. They show in Activity, the menu bar and the side panel beside Claude’s.
Its plan and a daily budget
Your Codex plan’s weekly limit, a daily budget, and how much of the week went on Codex cloud tasks, ChatGPT Work or another computer, with tokens by hour, day, session and model.
Its disk space, tidied safely
Codex’s session histories, archived sessions and caches join Storage, with a filter for All, Claude or Codex. Its sign-in, settings, plugins, skills and memories are never touched.
Nothing to install: it all comes from Codex’s own files on your Mac, and your prompts and Codex’s replies are never kept. More about the Codex beta
See exactly what a session did
Every tool call in order: the command or file, how long it took, and whether it failed. Filter to commands, files, or the calls that started something.
Beside it: its tokens, split into input, output and cache for each model it used, plus what it’s still running, the ports it opened, its CPU and memory over time, and every file it changed.
Terminal, IDE and desktop app sessions in one list, each once, with their titles, recently closed ones and Remote Control. The Claude Code command-line tool is all it needs; the desktop app adds its sidebar’s titles and groups.
With the Codex beta on, Codex sessions get a page of their own, laid out the same way.
The whole Mac, not just your AI agents
CPU for every core, memory with macOS’s own memory pressure and swap, network, disk and GPU, for everything running on the Mac.
The busiest processes by CPU and by memory, with Claude’s and Codex’s own marked, and charts that look back an hour, a day or a week.
Who started that VM?
Twelve container and VM tools checked, from Docker and Podman to Parallels, UTM, VMware and Apple’s own container tool.
Each one labelled Hook (recorded as it ran: certain), History (matched from a chat history: likely) or Not Claude, and anything a closed session left running at the top, ready to stop. With the Codex beta, filter to what’s Claude owned or Codex owned.
Dev containers, from VS Code or DevPod, get a section of their own, named after their project, and Claude sessions running inside them can report to the app too.
Know your budget before you hit the limit
Your plan’s limits for the current session and the week, with reset times, across all your devices, and for each model when you use the Claude desktop app. A gateway’s spend limit shows too.
The daily budget shares what’s left of your weekly limit over the working days left, so a quiet day leaves more for the rest, and an alert arrives at the levels you choose.
An estimate of how much of the week went on use from outside Claude Code on this Mac: chats, other Claude products, or another computer.
With the Codex beta on, Codex gets the same Usage page for its own plan.
This Mac’s tokens, with input, output and cache shown apart, for days and weeks that start when your plan resets, not at midnight or on a Monday, so they line up with your limits.
Always to hand, never in the way
Dock a panel to either side of any screen. It slides between a tab, a slim strip with counts and live bars, and the full panel, and slides away when you click elsewhere unless you pin it.
There’s a menu bar item too, with what’s happening now and what Claude started, and Codex’s sessions and budget beside Claude’s when the beta is on.
Nothing changes until you say so
The app works as soon as it opens. For Claude, two optional extras make it complete; it asks before each one, shows exactly what it adds, and removes them again from Settings. Codex needs neither.
The hook: certain links
VMs and containers are started through other apps, so they never show up under the session that asked for them. A small hook in Claude Code’s settings writes one line to a log on your Mac for each tool call, so everything is linked to its session for certain. It never blocks or changes what Claude does, and adds nothing to its context.
The companion plugin: plan limits
Your plan’s limits can only be read from inside a Claude session. The companion plugin reads them there, with per-model limits and your sidebar’s groups, and passes them to the app for the daily budget and alerts. It adds nothing to your conversations and uses no tokens.
Download Claude Doing?
Version 0.2.30, released 1 November 2026. Free, for macOS 26 or later.
Claude-Doing-0.2.30.dmg · 8.7 MB
SHA-256 c4af8829d17a258949e306eeb93e16c6c1f2ef20d5a32e3cd876a04250e6e590
Open the disk image and drag Claude Doing? to Applications. It keeps itself up to date: once a day it checks for a new release, signed by WhiteFish Creative, and asks before installing it. What’s new · All releases