Coordinate the coding agents you already use

You can use CLIO Coder to coordinate the coding agents you already have installed. Give a peer a focused assignment, follow a managed run where the connector supports it, and review its output before accepting the change.

See which peers CLIO Coder can use

clio-coder interop inspect --json
clio-coder configure --interop

The first command reports what CLIO Coder can find; the second configures interoperability. In a terminal conversation, /library interop shows the available connections. The interoperability guide covers the mode for each peer.

Choose managed work or an interactive handoff

The three commands answer different needs. Pick by whether you want a recorded run or a place to work with the peer yourself. An ACP peer is one CLIO Coder drives over the Agent Client Protocol; a headless target runs the peer's own CLI once for the task.

The panes tutorial covers the pane host. Do not infer that a pane completed a task because it opened. Do not infer that a run record contains every internal reasoning step or mediates every operation inside a peer-owned loop.

Give one bounded assignment

That last sentence is a task instruction, not an enforced boundary. For an enforced one, put --read-only before the task, as in /run --read-only <agent> <task>; an option typed after the task text becomes part of the task. CLIO Coder admits a read-only run only on a peer whose own sandbox refuses every write, and refuses it before launch on every other peer, ACP peers included.

Keep worker authority separate

A native worker, one of CLIO Coder's own agents, inherits the main session's level inside its own permit and OS sandbox. At contained yolo, which is yolo's default, workers are dispatched as at default; at unconfined yolo a mediated worker runs the yolo way within its dispatch scope. A read-only worker stays at default.

Managed peer dispatches run at default permissions, even when the main session uses yolo, and each external agent runs its own tool loop.

A read-only run must leave every file outside CLIO Coder's home unchanged. It is admitted only where the peer's own sandbox guarantees that, so check the peer before you rely on it.

ACP peers may own their tools. Explicitly permitting peer-owned tools changes what CLIO Coder can observe and mediate, so read the guide's permission limits before using such a peer on sensitive work. CLIO Coder's own shell commands and native workers' commands run in an OS sandbox when one is available. External peers keep their own authority.

Separate changes with a worktree

For supported headless dispatch, --worktree keeps a Git task branch for review. That helps you compare two proposed changes without mixing their working files.

A worktree is an organizational boundary. It does not confine a peer's filesystem or network access. Keep assignments narrow, inspect the branch and diff, and run the repository's checks before merging a result.

Review before combining

When comparing agents, give them the same task and evaluate the actual output. Record the model, connector, setup, check results, and any costs you can substantiate. CLIO Coder coordinating two peers does not make either one better.