Module 03 | Hand an agent a goal and walk away

Put the brake in another terminal

Type the full pause command with both mission and agent UUIDs before starting. Press Enter immediately after the running response.

Use two PowerShell windows.

A mission is a goal the agent works toward. You supply the objective, not fixed ordered steps.

Run in your terminal

armaraos orchestration quota <ORCHESTRATOR_UUID>

Confirm the same agent still reports three allowed subagents and depth two.

Run in your terminal

armaraos mission create --agent-id <UUID> --objective "<MARKDOWN_OBJECTIVE>" --json

A newly created mission is not running.

Run in your terminal

armaraos mission pause <MISSION_ID> --agent-id <UUID> --json

Type it in the second terminal and wait before pressing Enter.

Run in your terminal

armaraos mission start <MISSION_ID> --agent-id <UUID> --json

The live API requires --agent-id on these controls even though the help layout does not mark it required.

Run in your terminal

armaraos mission get <MISSION_ID> --agent-id <UUID> --json
armaraos mission list --agent-id <UUID> --json

No handoffs and zero tokens mean this run did not delegate. A state label is not proof of subagent activity.

The objective was inline markdown. No workflow file was authored.

Check it / pair both IDs

List missions for the orchestrator and identify the generated mission UUID, owner UUID, and current paused state.

Safety note

A mission can spend and create subagents once execution begins. Put a valid pause command in a second terminal before every first start.

Troubleshooting for this sitting

What you see	Likely cause	What to do
Start requires agent ID	Live API is stricter than help layout.	Add the owner name or UUID.
Awaiting input persists	Mission was not started.	Start with both IDs.
No delegation appears	No handoff was produced.	Check detail, quota, doctor, logs, then provider limits.
Wrong mission appears	IDs were mixed.	Pair mission and owner UUIDs.