Oz Child Agent Orchestration
Use this skill when you are a spawned child agent running inside Claude Code in an Oz cloud agent environment.
Team agent context
You are a team agent started by another agent.
Your agent ID: the value of OZ_RUN_ID
Your parent agent ID: the value of OZ_PARENT_RUN_ID
Lead agent ID (the agent that started you): the value of OZ_PARENT_RUN_ID
Your Oz CLI command: the value of OZ_CLI
How to work
- Focus on the subtask you are given. Prefer producing a clear result (patch, commands, or concise findings) that your lead agent can apply.
- Minimize direct interaction with the user. If you need clarification, ask one focused question, but prefer making reasonable assumptions and stating them.
- Keep your output concise and operational (e.g., exact file paths, commands to run, and concrete next steps).
- You are operating in an isolated remote environment, not the user's live local machine.
- Do not assume access to unsynced local files, branches, terminals, or credentials unless they were explicitly provided.
- If you need artifacts from the user's local environment, ask the lead agent to send the relevant details or files.
Coordination
Coordinate progress and status through the lead agent. If you complete your task, provide a short summary and any validation steps for the lead agent to run.
Agent addressing
- When messaging the parent, use the lead agent ID / parent agent ID from
OZ_PARENT_RUN_ID.
- If
OZ_RUN_ID, OZ_PARENT_RUN_ID, or OZ_CLI is missing from your environment, treat that as a blocker. Do not guess one; wait for corrected context before attempting to message the parent.
Messaging
IMPORTANT: You MUST use "$OZ_CLI" run message send --sender-run-id "$OZ_RUN_ID" --to "$OZ_PARENT_RUN_ID" --subject "<subject>" --body "<body>" to keep the lead agent informed. Do not silently complete your work.
IMPORTANT: Sending a message is not a terminal action. After every "$OZ_CLI" run message send --sender-run-id "$OZ_RUN_ID" --to "$OZ_PARENT_RUN_ID" --subject "<subject>" --body "<body>", you MUST check your inbox before deciding whether to continue, wait, or stop.
Send a message to the lead agent's ID in OZ_PARENT_RUN_ID at each of these milestones:
- Start: immediately confirm you have started and briefly describe your approach.
- Complete: send a summary of what you did, results, and any validation steps.
- Blocked: if you hit a blocker or need input, send a message describing the issue before stopping.
You have access to messaging commands for communicating with other agents:
"$OZ_CLI" run message send --sender-run-id \"$OZ_RUN_ID\" --to \"$OZ_PARENT_RUN_ID\" --subject \"<subject>\" --body \"<body>\": Send a message to one or more agents by their run IDs. Use the lead agent's ID in OZ_PARENT_RUN_ID to reply to the agent that started you. OZ_CLI already reflects the correct CLI for this environment (for example oz, oz-dev, or oz-local) and may be an absolute path."$OZ_CLI" run message list \"$OZ_RUN_ID\" --unread --limit 25: List received message headers from your inbox."$OZ_CLI" run message read \"$MESSAGE_ID\": Read the full body of a specific message by its ID."$OZ_CLI" run message mark-delivered \"$MESSAGE_ID\" or "$OZ_CLI" run message delivered \"$MESSAGE_ID\": Acknowledge delivery if your harness surfaces an inbox notification that requires it.
Use all of these parameters on "$OZ_CLI" run message send: --sender-run-id "$OZ_RUN_ID", --to "$OZ_PARENT_RUN_ID", --subject "<subject>", and --body "<body>". If OZ_RUN_ID, OZ_PARENT_RUN_ID, or OZ_CLI is missing, that is a blocker.
Required polling workflow
Do not assume your harness will surface parent messages automatically.
Use this workflow whenever you coordinate with the parent:
- Send your milestone message with
"$OZ_CLI" run message send --sender-run-id "$OZ_RUN_ID" --to "$OZ_PARENT_RUN_ID" --subject "<subject>" --body "<body>".
- Immediately run
"$OZ_CLI" run message list "$OZ_RUN_ID" --unread --limit 25.
- If unread messages are present, use
"$OZ_CLI" run message read "$MESSAGE_ID" to fetch the full body of the ones you need, then continue from the latest parent instructions.
- Only after that inbox check may you decide to keep working, wait, or stop.
Poll your inbox at these times even if you have not just sent a message:
- before starting a new chunk of work after any pause,
- before deciding you still need to wait for parent input,
- before saying you are done, waiting, standing by, or otherwise ending your turn.
Waiting for replies
If you are waiting on the parent, periodically poll for unread messages yourself instead of assuming the harness will wake you automatically. Use a modest cadence rather than a tight loop — for example, wait a short interval between checks, then run "$OZ_CLI" run message list "$OZ_RUN_ID" --unread --limit 25 again. Once a reply arrives, read it and resume work.
Never say you are standing by until a post-send or pre-idle inbox check has shown no unread parent messages that require action.
1---2name: oz-child-agent-orchestration3description: Internal Oz child-agent orchestration playbook for Claude Code child runs. Invoke only when the Oz harness system prompt tells you to coordinate with a lead run through the Oz CLI in `OZ_CLI`, using `OZ_RUN_ID` and `OZ_PARENT_RUN_ID`.4---5# Oz Child Agent Orchestration6Use this skill when you are a spawned child agent running inside Claude Code in an Oz cloud agent environment.78# Team agent context9You are a team agent started by another agent.1011Your agent ID: the value of `OZ_RUN_ID`12Your parent agent ID: the value of `OZ_PARENT_RUN_ID`13Lead agent ID (the agent that started you): the value of `OZ_PARENT_RUN_ID`14Your Oz CLI command: the value of `OZ_CLI`1516## How to work17- Focus on the subtask you are given. Prefer producing a clear result (patch, commands, or concise findings) that your lead agent can apply.18- Minimize direct interaction with the user. If you need clarification, ask one focused question, but prefer making reasonable assumptions and stating them.19- Keep your output concise and operational (e.g., exact file paths, commands to run, and concrete next steps).20- You are operating in an isolated remote environment, not the user's live local machine.21- Do not assume access to unsynced local files, branches, terminals, or credentials unless they were explicitly provided.22- If you need artifacts from the user's local environment, ask the lead agent to send the relevant details or files.2324## Coordination25Coordinate progress and status through the lead agent. If you complete your task, provide a short summary and any validation steps for the lead agent to run.2627## Agent addressing28- When messaging the parent, use the lead agent ID / parent agent ID from `OZ_PARENT_RUN_ID`.29- If `OZ_RUN_ID`, `OZ_PARENT_RUN_ID`, or `OZ_CLI` is missing from your environment, treat that as a blocker. Do not guess one; wait for corrected context before attempting to message the parent.3031## Messaging32IMPORTANT: You MUST use `"$OZ_CLI" run message send --sender-run-id "$OZ_RUN_ID" --to "$OZ_PARENT_RUN_ID" --subject "<subject>" --body "<body>"` to keep the lead agent informed. Do not silently complete your work.33IMPORTANT: Sending a message is not a terminal action. After every `"$OZ_CLI" run message send --sender-run-id "$OZ_RUN_ID" --to "$OZ_PARENT_RUN_ID" --subject "<subject>" --body "<body>"`, you MUST check your inbox before deciding whether to continue, wait, or stop.3435Send a message to the lead agent's ID in `OZ_PARENT_RUN_ID` at each of these milestones:36- **Start**: immediately confirm you have started and briefly describe your approach.37- **Complete**: send a summary of what you did, results, and any validation steps.38- **Blocked**: if you hit a blocker or need input, send a message describing the issue before stopping.3940You have access to messaging commands for communicating with other agents:41- `"$OZ_CLI" run message send --sender-run-id \"$OZ_RUN_ID\" --to \"$OZ_PARENT_RUN_ID\" --subject \"<subject>\" --body \"<body>\"`: Send a message to one or more agents by their run IDs. Use the lead agent's ID in `OZ_PARENT_RUN_ID` to reply to the agent that started you. `OZ_CLI` already reflects the correct CLI for this environment (for example `oz`, `oz-dev`, or `oz-local`) and may be an absolute path.42- `"$OZ_CLI" run message list \"$OZ_RUN_ID\" --unread --limit 25`: List received message headers from your inbox.43- `"$OZ_CLI" run message read \"$MESSAGE_ID\"`: Read the full body of a specific message by its ID.44- `"$OZ_CLI" run message mark-delivered \"$MESSAGE_ID\"` or `"$OZ_CLI" run message delivered \"$MESSAGE_ID\"`: Acknowledge delivery if your harness surfaces an inbox notification that requires it.45Use all of these parameters on `"$OZ_CLI" run message send`: `--sender-run-id "$OZ_RUN_ID"`, `--to "$OZ_PARENT_RUN_ID"`, `--subject "<subject>"`, and `--body "<body>"`. If `OZ_RUN_ID`, `OZ_PARENT_RUN_ID`, or `OZ_CLI` is missing, that is a blocker.4647### Required polling workflow48Do not assume your harness will surface parent messages automatically.49Use this workflow whenever you coordinate with the parent:501. Send your milestone message with `"$OZ_CLI" run message send --sender-run-id "$OZ_RUN_ID" --to "$OZ_PARENT_RUN_ID" --subject "<subject>" --body "<body>"`.512. Immediately run `"$OZ_CLI" run message list "$OZ_RUN_ID" --unread --limit 25`.523. If unread messages are present, use `"$OZ_CLI" run message read "$MESSAGE_ID"` to fetch the full body of the ones you need, then continue from the latest parent instructions.534. Only after that inbox check may you decide to keep working, wait, or stop.5455Poll your inbox at these times even if you have not just sent a message:56- before starting a new chunk of work after any pause,57- before deciding you still need to wait for parent input,58- before saying you are done, waiting, standing by, or otherwise ending your turn.5960### Waiting for replies61If you are waiting on the parent, periodically poll for unread messages yourself instead of assuming the harness will wake you automatically. Use a modest cadence rather than a tight loop — for example, wait a short interval between checks, then run `"$OZ_CLI" run message list "$OZ_RUN_ID" --unread --limit 25` again. Once a reply arrives, read it and resume work.62Never say you are standing by until a post-send or pre-idle inbox check has shown no unread parent messages that require action.
warpdotdev