# Worker loop Use when you are the worker: a task was claimed for you, or you were told to claim one. `$MU_AGENT_NAME` (injected at spawn) resolves identity; adopted panes fall back to the pane title. In a worker pane, bare `mu task claim ` works. In the unregistered orchestrator pane it errors; use `--self`, `--for `, or `mu agent adopt `. ```bash mu me mu me next mu task show ; mu task notes mu task claim --evidence "starting; read notes" mu task note "FILES: ...\nCOMMANDS: ... (exit codes)\nDECISION: ...\nVERIFIED: ..." mu task close --evidence "tests pass: ..." # LAST action ``` Follow [test-health](test-health.md) for fast iteration checks, targeted slow checks before close, gate records, and cheap bug red-green. Include the gate records in your final note; adding tests uses its test-level and timing rules. The note follows the task note contract in SKILL.md. Keep each tool call to minutes (short batches, waits with a timeout): steering reaches you only between tool calls. Commit before you close: the orchestrator cherry-picks your commits, not your tree. A review or audit task records each problem per [findings ยง Record](findings.md#record). Done when your changes are committed in the workspace, the task note holds FILES, COMMANDS (with exit codes), VERIFIED and applicable gate records, and `mu task close` succeeded as your last action. Skipping close makes the orchestrator's wait hang. Won't do it: `close --as wontfix --why "..."`.