Which Claude Code or Codex session is waiting for my input?
Each terminal shows only its own agent, so with several running you find the one waiting on you by checking every pane. ACTVT keeps track of every session and sends an alert naming the session that is waiting and what it is waiting for, such as “Waiting for your OK to run Bash”. Since ACTVT 1.4.11 it reads the status Claude Code 2.1.221 and later writes for each session, so a permission prompt or a question shows as waiting at ACTVT’s next check, about half a minute in this video, instead of after 90 seconds of quiet. Codex and older Claude Code versions still use the 90-second rule. Click the alert to open the session, and its window button brings the exact terminal or tmux pane forward. Headless runs (claude -p) never show as waiting, because nobody is sitting at them.
0:564 chapters
Step by step
0:00Two agents
On a test Mac, two agents. In docs, a headless run writes a README on its own. In storefront, Claude Code in its default mode, which asks before it runs a command. docs finishes, and ACTVT says so.
0:13Look away
Then a task in storefront that needs a command. You switch to something else. Behind it, Claude stops and asks to run rm -rf (this wait is shown at 2×).
0:33It needs you
ACTVT says which session is waiting, and for what: here 28 seconds after the prompt.
0:39Jump to it
Click the alert: ACTVT opens that session, and its window button brings the terminal forward, on the exact tmux pane, at the prompt it’s waiting on. Approve it, and it carries on. Since 1.4.11 ACTVT reads Claude Code’s own status (2.1.221+); Codex and older versions still need 90 seconds of quiet.
Questions
- How fast does ACTVT notice?
- For Claude Code 2.1.221 and later, at its next check after the prompt appears: 28 seconds in this video. Codex and older Claude Code versions are flagged after 90 seconds of quiet.
- Can I jump to it?
- Yes. Click the alert to open the session, then its window button brings the exact terminal or tmux pane forward.
- Does it alert while I’m looking at the terminal?
- No. If the agent’s terminal is the app in front, you are already looking at the prompt, so ACTVT stays quiet.
More tutorials
All tutorials →
1:24Every machine you code on
See Claude Code, Codex and pi sessions from all your machines over SSH
Start Claude Code on another Mac over SSH, and you can follow the session from your own Mac while it runs and read the whole transcript when it’s done.
3:42Leftover ports
Find and kill the dev server Claude Code or Codex left running
Claude Code starts a dev server and then quits, and port 3000 stays taken. ACTVT shows you the server whose session is gone and lets you free the port safely.
0:48A plan-aware agent
Check your Claude and Codex plan limits before a long agent job
Before a two-hour job, Claude Code asks ACTVT how much of your plan is left. You can see the same limits in ACTVT, along with when each one resets.
Try it on your own agents
ACTVT is free to start, and reads the session files Claude Code, Codex CLI and Pi already write. Nothing to configure.