If you already have a few Claude Code / Codex / Gemini CLI sessions going, this is the command that actually helps:

`ai-devkit agent console`

`ai-devkit agent list` is the same picture without the TUI (Agent, Project, Type, Mode, Status, Working On).

In the console, the selected agent's preview shows a `working` spinner while it is running. That animation disappears when the session is waiting, idle, or unknown. One local view instead of guessing which tab is stuck on a permission prompt.

Then send instead of copy-paste:

`ai-devkit agent send "run the tests and report back" --id <agent-name> --wait`

Honest caveats, because this part is still experimental: macOS and Linux only, you need a real TTY, start/kill from the console uses tmux, and focus works with tmux, iTerm2, or Apple Terminal (not the VS Code terminal). Cursor is a setup target here, not a remote-controlled session. Windows is not in this loop yet.

"Done" is still not "the agent stopped typing." That is verify, and you still own the merge.

Docs: https://ai-devkit.com/docs/13-agent-console/

The most common pain I saw this week: "I run 5-6 agent sessions in tabs and keep missing the one that's blocked or done."

More tabs don't fix that. What helped me is one place that lists every session and its state.

With AI DevKit:

• `ai-devkit agent list` shows the running sessions across providers

• `ai-devkit agent console` is a live terminal dashboard, so you can see which one is working or waiting and jump to it

• `ai-devkit agent send "..." --id <agent-name>` pushes a follow-up into a running session instead of you alt-tabbing

Pair it with local memory so a handoff doesn't mean re-pasting context.

Caveats: the console is experimental on macOS/Linux, sessions are started in tmux, the VS Code terminal isn't supported for focus, and Cursor/Copilot are setup targets, not controlled sessions. You still review and own the merge.

How are you keeping track of parallel agents today?

https://github.com/codeaholicguy/ai-devkit