CLI Manager vs Mirror CLI

CLI Manager

An agent can open visible terminal sessions, type into them, wait and read the screen through 12 typed MCP tools or a documented REST API, and the user can take any session back. The API reaches every open session once enabled, the app runs only on macOS, and none of the last 35 CI runs on the main branch passed.

Mirror CLI

Mirror CLI is Apache-2.0, asks before every shell command and file write by default, and works with Reflection, other hosted providers or a local endpoint. It is a one-day-old 0.1.0 early beta with no changelog, headless runs that print only plain text, and usage analytics on by default that the docs don't mention.

CLI Manager

1. Ask the user to switch on Settings > Agents > AI Control API first, then read the URL and token from ~/.climanager/control-api.json
2. On 409 awaiting_input, read the screen and answer with keys such as ["down","enter"]. Leave folder-trust and permission choices to the user
3. Stop using a session on 409 disconnected. The user took it back
4. Treat timedOut: true from wait as still running, not as a failure, and wait again
5. Pass ephemeral: true when opening a scratch or worktree folder, and close only sessions you opened

Mirror CLI

1. Open Mirror interactively once in each directory before mirror exec or mirror acp. Both refuse to run until the usage and folder notices are accepted
2. Pass --approval-mode auto to mirror exec only inside a container or VM. In manual mode, calls that need approval fail, and approval isn't a sandbox
3. Set --max-iterations on unattended runs. Turns are unlimited by default
4. Check the result with your own tests. exec returns 0 whenever it prints an answer
5. Never share logs recorded with --log-level debug. The docs say they contain request headers with the API key