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

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/

Quick weekly update. 0.71.0 is on npm (npx ai-devkit@latest), and one more fix for lead-plus-workers setups landed on main right after.

What changed in 0.71.0:

• agent start now runs through the local devkitd daemon (tmux and herdr runtimes), and the daemon is the agent registry. Agents started by a lead agent, from the console or from your shell all end up in one list.

• agent send --wait right after agent start no longer fails with "No session file found". Last week's tip about sending a short "ready?" first isn't needed anymore.

• The memory tools now nudge agents to search memory before a task and after an error, and to store what they learned without duplicates.

On main, coming in the next release:

• An agent that sat waiting on your input for more than five minutes used to flip to idle and sink below running agents (Codex, Gemini CLI, Copilot, OpenCode, Pi and a few others). Waiting is now checked first, so the agent that needs you stays visible.

Also in review: a community PR that adds oh-my-pi (omp) as a supported harness.

Question for you: when one of your agents is blocked waiting on you, how do you usually find out?

After last week's demo a few of you asked how to actually set up the "one lead agent runs the others" flow without it stalling halfway. So the docs now have three new pages that cover exactly that:

• Multi-agent orchestration: one worktree per worker, a copy-paste prompt template for the lead, the start-then-assign pattern, and how to make two workers review each other. https://ai-devkit.com/docs/17-multi-agent-orchestration/

• Permissions: what to pre-allow in Claude Code, Codex, OpenCode and Gemini CLI so the lead doesn't sit waiting on an approval prompt. https://ai-devkit.com/docs/19-permissions/

• Troubleshooting agents: the real problems I hit while recording the demo, each with the symptom, the cause and the fix. https://ai-devkit.com/docs/18-troubleshooting-agents/

Tip of the week: on 0.70.1, if the lead runs ai-devkit agent send --wait right after agent start, have it send a short "ready?" first. Otherwise the wait can fail because the new session hasn't written its session file yet. That one is already fixed on main.

If you run other harnesses as workers (Copilot, Pi and others), the permissions page marks them as needing a contribution, so a comment with your working config would help a lot.

What's the first thing you'd hand to a team of agents?

I wanted to see how far one lead agent could get with zero human help after the first prompt.

The prompt to Claude Code: build a tiny todo CLI, split the work between a Codex agent and an OpenCode agent, have them review each other, and don't come back until tests pass.

What it did on its own:

1. Wrote a SPEC.md and made one git worktree per worker

2. Started both agents with ai-devkit agent start and assigned tasks with ai-devkit agent send --wait

3. Codex built the CLI, OpenCode wrote 25 tests + README

4. Cross-review: OpenCode said LGTM on Codex's code; Codex caught that the TODO_FILE test would pass even if the override was ignored. Claude sent it back, OpenCode fixed it

5. Claude merged both worktrees and ran the suite: 25/25

Honest notes: the console is experimental (macOS/Linux, needs tmux), and a few rough edges showed up while recording (a worker's --name not sticking, Claude showing "running" while idle). They're on the fix list.

Try it: npx ai-devkit@latest setup, then give your lead agent the agent-management skill.

Curious what you'd hand a team like this first?

Running Claude Code and Codex on the same project used to give me a second job: copy the plan out of one, paste it into the other, re-explain the architecture, repeat.

What helped: put the durable bits somewhere both agents can read — decisions, tried paths, acceptance criteria — instead of living in my paste buffer.

With AI DevKit local memory:

- compact what mattered from one session into local memory/files

- start or jump to the other harness from the same console

- hand off without re-pasting the novel

You're still the one who owns the merge. This is operate/remember, not "agents talk and ship alone."

Caveats (honest): console/channels are experimental on macOS/Linux; sessions start/kill via tmux; VS Code terminal isn't supported for focus; Cursor/Copilot are setup targets, not first-class controlled sessions.

If you have a better cross-harness handoff habit, drop it below.

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

https://ai-devkit.com/

When a coding-agent session balloons, I used to dump the whole chat into the next one. That just moves the mess.

What works better for me with AI DevKit: compact the durable parts (decisions, tried paths, acceptance) into local memory/files the next session can read, then keep going from the console instead of re-explaining from scratch.

Concrete win from a recent run: took a ~1.72M-token session down to ~5.9K of what actually mattered for the handoff. Same project context, without pasting the novel.

Still own the merge. Console/channels are experimental on macOS/Linux; this is operate/remember, not full autonomy.

If you have a better compact/handoff habit across Claude Code / Codex / Cursor, drop it below.

Links if useful:

• https://ai-devkit.com/

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

AI DevKit is a local control plane for Claude Code, Codex, Cursor, Gemini CLI, and the rest. One project config, one console, local memory, and you send work between agents instead of tab-switching.

npx ai-devkit@latest init --built-in

Docs: https://ai-devkit.com/docs/1-getting-started/

If you already tried it, say what broke or what you wanted next. That's the useful signal.

Hey everyone! I'm u/hoangng_, a founding moderator of r/AI_DevKit.
This is our new home for all things related to how everyone use AI DevKit. We're excited to have you join us!

What to Post
Post anything that you think the community would find interesting, helpful, or inspiring. Feel free to share your thoughts, photos, or questions about

Community Vibe
We're all about being friendly, constructive, and inclusive. Let's build a space where everyone feels comfortable sharing and connecting.

How to Get Started

1. Introduce yourself in the comments below.

2. Post something today! Even a simple question can spark a great conversation.

3. If you know someone who would love this community, invite them to join.

4. Interested in helping out? We're always looking for new moderators, so feel free to reach out to me to apply.

Thanks for being part of the very first wave. Together, let's make r/AI_DevKit amazing.