Agent Standup band

Agent Standup band puts a line above your Claude Code prompt when another Claude Code session on the same computer is stuck waiting for you, on a permission menu or a question. A toast also tells you when a session starts waiting or finishes its turn, so you can stay in the session you are working in. It reads only the small status files Claude Code keeps for its sessions, runs no model and sends nothing.

The band is one piece of Agent Standup, an app that turns the session files of Claude Code, Codex and Mistral Vibe into a live, animated team call: the lead and each subagent are characters at their desks, the one at work shares its screen with the real commands and diffs, and a Sessions board sorts every session by state. The app comes as a VS Code extension (also on Open VSX for Cursor and Windsurf), a terminal command and a macOS desktop app, runs locally, and costs no tokens unless the call is translated or you turn on its jokes. The band is the part that lives inside Claude Code, and it works without the app or Node.js.

What it does

• One line per waiting session, up to three, then “and N more”. Each line names the session by its folder, the name you gave it if any (not the title Claude Code generated) and the app it runs in when that is VS Code or the desktop app, followed by “needs an approval” or “needs an answer”.
• A Hide button puts the current set of waits away. The band comes back when another session starts waiting or what one waits for changes.
• Toasts: one when a session starts waiting for you, one when a session goes from busy to idle (“has finished: your turn there”). Sessions that were already waiting when your session started are shown on the band but not announced.
• No false alarms from your own session or from a dialog you opened yourself in another one (/model, /config). The band also steps aside while Claude Code shows a survey above the prompt.

Install

Needs Claude Code 2.1.294 or later. The author says earlier versions load the plugin and do nothing.

claude plugin marketplace add Atoll92/agent-standup
claude plugin install agent-standup-band@double-geste

Restart Claude Code or run /reload-plugins. There is nothing to run: the band appears on its own the next time another session waits for you. From inside Claude Code, the author’s one-liner does the same: /plugin install agent-standup-band --marketplace Atoll92/agent-standup.

The double-geste marketplace also carries agent-standup, a separate plugin that is not this band. It adds two skills, /agent-standup:open, which starts the Agent Standup app and opens the call in your browser, and /agent-standup:status, which says in one line who is working and who needs you, and it runs the app’s npm package to do so. The band’s bottom line points to /agent-standup:open, which works only with that second plugin installed (claude plugin install agent-standup@double-geste).

How it works

Every 4 seconds, the module lists ~/.claude/sessions (or the sessions folder under CLAUDE_CONFIG_DIR) and reads each <pid>.json file there: the session id, its folder, its name, the app that runs it, and whether it is busy, idle or waiting, and on what. It never opens transcripts, so it does not see what you or Claude wrote. Sessions a program started with claude -p are skipped, because their questions go to that program; Agent SDK apps such as Zed are kept, since a person may be answering their menus.

A session that crashes leaves its status file behind. So, for the sessions that say they are waiting, the module runs ps -o pid= -p <pids> through Claude Code’s process call, with a 5-second timeout, and drops any whose process is gone. That is the only command it runs.

What it knows stays in memory. It writes no file, makes no network request and calls no model, so it uses none of your plan.

Limitations

• It watches Claude Code sessions only. Codex and Mistral Vibe sessions show in the Agent Standup app, not on the band.
• It reads the config directory of the session it runs in, so a session started with a different CLAUDE_CONFIG_DIR does not appear. Neither does a Claude Code started from inside another Claude Code session, which writes no status file.
• On Windows there is no ps, so the band takes every status file at its word: a session that crashed while waiting can keep its line.
• Changes reach the band within 4 seconds, not at once.
• The author documents the band in the terminal and in the Claude desktop app’s Code tab. In the chat panel of VS Code, where mods do not draw, the Agent Standup extension shows the same waits in its status bar.