CLI Manager - Let one AI agent open and drive your other CLI agents

by•
CLI Manager now has an AI Control API. Claude Code, Codex or any script can open sessions in CLI Manager, send prompts, wait, and read the screen - in terminals you can watch. Sessions an AI is driving turn green in the sidebar, the orchestrator gets a crown, and Disconnect AI takes control back anytime. Local only (REST + MCP on 127.0.0.1), off by default. Plus everything from launch #1: Claude Code, Codex and Gemini CLI in one sidebar. Free, MIT open source, macOS.

Add a comment

Replies

Best
What if one AI agent could run the rest of them? Last December I launched CLI Manager to keep all my CLI agents in one place. After that I kept doing the same thing by hand: open a session per repo, paste the task, check back on each one. So I added an AI Control API. Now my Claude Code session opens one session per repo, they work in terminals I can watch, and it reports back in a table. If anything looks off, I click Disconnect AI and take over. It's also free and MIT open source now — the two things people asked about most last time. macOS only for now. What would you hand off to an orchestrator first?

Congrats, CLI Manager team! Nice to be launching alongside you today. Benson is live too: . Would appreciate a comment or some support if you get a spare minute. Hope it's a good day for you!

Hey, love that the control API is off by default. First thing I'd hand off is the boring loop: run the tests, read the failure, re-prompt. The hard part is knowing when the orchestrator should stop and pull in a human. Are you planning hooks so it can check "is this actually done" against the original task? That's where most of my multi-agent runs drift.