fanout

# fanout — safe parallel execution Use ONLY for subtasks that are parallel-safe (no shared files, no ordering dependency). ## Procedure 1. Per task, create an isolated worktree: `sys_os_shell("git worktree add .worktrees/<task_id> -b polly/<task_id>")`. Record the worktree path + branch in the registry (`.polly/registry.json`). 2. Dispatch one implementation sub-agent per task, scoped to its worktree: `sys_session_send(agent="claude_code"|"codex"|"opencode"|"cursor"|"hermes"|"agy", title="<task_slug>", args={purpose: "implement", input: "<task + acceptance contract + worktree path>"})`. Use a short task-based title such as `auth-refactor` or `fix-sse-error`, never the raw vendor name. State the scope and that it must work only inside `.worktrees/<task_id>`. The worker drives the task to green and opens its OWN PR for the branch. Every commit the worker authors must end with a blank line followed by the exact co-sign trailer as its final line — `Co-authored-by: omnigent <noreply@omnigent.ai>`. For a long-running `claude_code` or `codex` implementation with an explicit completion condition, the `input` may instead be one standalone `/goal <condition>` command containing that same task, worktree, acceptance contract, green gates, and PR requirement. Do not use child goal mode for other workers or non-implementation purposes. Record each handle's `conversation_id` in the registry. Emit the worktree + `sys_session_send` tool ...