CLI Subagent

Coordinate Claude or Codex as a subagent under the global Collaboration policies. Resolve the execution interface before starting CLI readiness.

Select Execution Interface

Include the calling workflow’s session lifecycle and retained-context requirements when deciding whether a host-managed exchange or CLI fallback is eligible. For iterative reviews, apply subagent-review-flow’s continuity and recorded reviewer-role transfer requirements before selection. Use the global Host-managed execution policy for host interface preferences. Fresh-session-only support is a capability limit, not permission to change mandated reviewer selection or interfaces.

When a task requests a Claude Code or Codex CLI agent, prefer a host-managed delegate of that provider when the host’s documented interface supports the requested model and explicit reasoning effort selection. When the user, calling workflow, or Host-managed execution selects a top-level thread, use it in place of a delegate under the same provider, model, and effort checks. An agent using the same model in the host’s own agent harness does not qualify. Establish the provider, resolved model, and effort match without guessing aliases, defaults, or inheritance. For omitted model or effort settings, use only the model and effort defaults in Claude CLI or Codex CLI. Their execution requirements apply only after selecting CLI execution.

A CLI name alone identifies the requested provider. Keep the CLI interface when the user expressly requires it or the task tests or debugs the CLI. Otherwise, when no eligible host-managed exchange is available, use the CLI workflow where permitted. If the host prohibits that fallback, report the limitation rather than substituting another provider or settings. Interface selection doesn’t expand authorization or change the authorized disclosure destination, account, or permission boundaries.

Apply Bound the Exchange to either interface. For an eligible host-managed exchange, use agent-task-relay for assignments, subagent-review-flow for reviews, and the host’s dispatch, monitoring, continuation, and permission procedures. The remaining sections govern actual CLI exchanges only.

Bound the Exchange

• Authority: An explicit collaboration request authorizes only the covered exchange with the requested participant. Loading this skill doesn’t authorize additional disclosure. Preserve all governing scope, approval, and security gates in the coordinator’s thread.
• New user input: Treat new user questions and notes as addressed to the coordinator by default. An active exchange doesn’t authorize forwarding them. Share only information needed for the existing assignment, or additions the user explicitly asks to involve the participant in.
• Recursion: A participant launched through this workflow, and every delegate beneath it, must not start or resume another CLI subagent through claude, codex, or any other agent CLI, directly or indirectly, or use host-managed substitution to start another provider exchange. Ordinary native subagent delegation remains permitted on both sides within the inherited assignment boundaries. Carry this boundary into either interface’s assignment.
• One unit per session: Assign work to one provider session as you would to a native subagent, under the same inherited boundaries. The participant owns its native subagents and background commands, so during normal operation the coordinator neither tracks nor cancels them individually.

Establish Readiness

Under the global CLI subagent readiness policy, load Session Coordination for lifecycle evidence reuse, resumption, monitoring, and task-specific limits, together with the participant’s reference for runtime defaults and launch, resume, and stop procedures: Claude CLI or Codex CLI. The shared readiness procedure determines whether applicable evidence suffices or a substantive or readiness-only exchange is needed.

Prepare the Assignment

Use agent-task-relay to compose assignments and follow-ups. Include the recursion boundary and active progress and command limits in the assignment. For follow-ups, apply the retained-context checks.

Dispatch and Coordinate

1. Start a fresh conversation by default, one per independent assignment when the work splits. Resume a specific full session UUID when continuing the assigned work, including after its readiness-only exchange. Follow the participant reference’s launch and resumption procedures.
2. Check pending sessions opportunistically, observing all of them in one call regardless of participant. Don’t replace useful concurrent work with a blocking polling script.
3. When CLI sessions become the last outstanding dependencies, await those same sessions together under the inactivity policy. This is a change in the coordinator’s scheduling, not a foreground relaunch.
4. Retrieve the complete response for each session’s latest requested turn before treating it as finished.

Background execution doesn’t itself give the host a completion callback or the ability to wake a yielded thread. Use only scheduling capabilities the host actually provides. Don’t promise automatic follow-up after yielding when none exists, and don’t leave a running session without an identified monitoring owner.

Resolve Feedback

Apply the global Findings policy. For delegated reviews, use subagent-review-flow as for native subagents. Use the resumption procedure for continued work, including required re-review.

Finish or Pause

Follow the error and stopping procedure. Report the integrated outcome under the shared communication policies. Identify still-running work and its monitoring owner when applicable.