`homeboy agent-task` command reference

Generated from the clap command tree. This page is the complete synopsis, argument, flag, and subcommand surface for this command family.

Concepts, recipes, and contracts are hand-written in docs/commands/agent-task.md.

Global flags apply to every command and are documented once in the root command reference.

homeboy agent-task

sh
homeboy agent-task <COMMAND>

Run generic agent task plans

SubcommandSummary
homeboy agent-task doctorno help text
homeboy agent-task cookSubmit an agent task, run its gates, and open a pull request
homeboy agent-task cook-continueContinue a detached Cook from its durable Cook ID or provider attempt ID. The persisted recipe supplies the original prompt, transport, gates, worktree, and disclosure policy
homeboy agent-task loopno help text
homeboy agent-task run-planno help text
homeboy agent-task runno help text
homeboy agent-task run-nextno help text
homeboy agent-task submitno help text
homeboy agent-task statusno help text
homeboy agent-task listno help text
homeboy agent-task activeno help text
homeboy agent-task reconcilePreview or apply reconciliation for one durable run
homeboy agent-task reconcile-recordsno help text
homeboy agent-task latestno help text
homeboy agent-task logsno help text
homeboy agent-task artifactsno help text
homeboy agent-task retained-artifactsDiscover or attach selected outputs retained in a terminal Lab Cook workspace
homeboy agent-task evidenceno help text
homeboy agent-task diagnoseno help text
homeboy agent-task runtime-recoverRecover a missing or corrupted immutable controller runtime pin
homeboy agent-task runtime-validateValidate controller runtime eligibility without executing provider work
homeboy agent-task replay-provider-boundaryno help text
homeboy agent-task cancelno help text
homeboy agent-task resumeno help text
homeboy agent-task retryno help text
homeboy agent-task fanoutno help text
homeboy agent-task reviewno help text
homeboy agent-task promoteno help text
homeboy agent-task adoptAdopt an immutable commit candidate through a tracked cook’s normal gates and finalization
homeboy agent-task finalize-prno help text
homeboy agent-task acceptRecord an independent, durable acceptance verdict for a candidate
homeboy agent-task gate-feedbackno help text
homeboy agent-task providersno help text
homeboy agent-task promptsno help text
homeboy agent-task contractno help text
homeboy agent-task compile-loopno help text
homeboy agent-task authno help text
homeboy agent-task controllerno help text

homeboy agent-task doctor

sh
homeboy agent-task doctor [OPTIONS]

This command declares no clap help text, so no description can be generated for it.

OptionValueDescription
--runner<RUNNER>no help text
--backend<BACKEND>no help text
--selector<PROVIDER_ID>no help text
--path<PATH>no help text
--extension<EXTENSION>no help text
--require-tool<TOOL>no help text
--secret-env<ENV>no help text
--repairflagno help text

homeboy agent-task cook

sh
homeboy agent-task cook [OPTIONS]

Submit an agent task, run its gates, and open a pull request.

Provide the work with one --prompt and optional --goal framing, point --to-worktree at the existing worktree to edit (that checkout is authoritative — the agent’s changes, the --verify gates, and the PR all operate on it), and give one or more --verify commands that must pass in that worktree before promotion. Cook then commits, runs the deterministic gates, and finalizes a --base-targeted PR (use --no-finalize to stop before opening the PR). Repeatable --verify gates all run; the run retries up to --max-attempts times. Use agent-task fanout cook-batch for independent task waves.

WAIT POLICY: Cook always persists a durable run id before materialization, so a returned command is not by itself proof of a completed cook.

--wait observes until the lifecycle is terminal and returns the terminal Cook report. This is the default when neither flag is passed.

--detach-after-handoff returns once the run is durably accepted. Its result describes a submission, not an outcome.

Do not infer the wait policy from client interactivity. An orchestration client that needs one predictable contract should pass the flag rather than rely on the default, and read the terminal outcome from agent-task status <run-id> in either case.

OptionValueDescription
--prompt<PROMPT>Inline prompt, @<path> to read a file, - to read stdin, or @prompt:<id> for a stored prompt
--cwd<PATH>Existing local repo checkout or worktree path to cook in
--workspace<ID_OR_PATH>Homeboy workspace ID or existing local workspace path to cook in
--repo<REPO>Repo/component slug for metadata and task grouping, e.g. sample-plugin
--task-url<URL>Issue, PR, or tracker URL the task is cooking
--backend<BACKEND>Executor backend to request. Defaults to the configured coding backend
--selector<PROVIDER_ID>Optional provider id when more than one provider exists for the backend
--model<MODEL>Optional model override passed through to the provider
--secret-env<ENV>Secret environment variable name to hydrate for the provider. Repeatable
--concurrency<N>Maximum number of task cells to run at once
--run-id<ID>Optional durable run id. Generated when omitted
--provider-config<JSON>Provider config JSON object, @file, or – for stdin. Merged with workspace metadata
--client-context<JSON>Opaque client context JSON object, @file, or – for stdin
--max-provider-executions<N>Maximum total provider executions per task, including same-provider retries and provider rotations. --attempts 1 runs exactly once
--max-same-provider-retries<N>Same-provider retries allowed after the first provider execution
--max-provider-rotations<N>Cross-provider rotations allowed after the first provider execution
--queue-onlyflagPersist the run for a daemon/runner but do not execute immediately
--timeout-ms<MS>Provider wall-clock timeout in milliseconds. Defaults to Homeboy’s provider timeout
--candidate-completion<POLICY>Completion rule for isolated candidates: wait for all results (default) or promote the first successful candidate
--goal<TEXT>One-line statement of what a successful cook must achieve. Recorded as framing metadata for the provider task and used for review. Without –prompt, it supplies the one provider task
--to-worktree<HANDLE>Workspace handle the cook edits, verifies, and finalizes into (e.g. repo@branch-slug). Existing destinations are reused. A missing managed destination is created through its configured provider when –repo, –base, –head, and –task-url declare explicit intent
--provider-command<COMMAND>Deprecated promotion apply-provider command string. Migrate --provider-command 'provider --flag value' to --provider-argv provider --provider-argv --flag --provider-argv value; argv preserves exact arguments without shell splitting. The provider reads stdin request schema homeboy/agent-task-promotion-apply-request/v1 and writes response schema homeboy/agent-task-promotion-apply-response/v1 with workspace_path.
--provider-argv<ARG>Promotion-only apply-provider invocation argument. Repeat once per exact argv element: the first is the executable and later values are its arguments; values are never shell-split. This cannot select an executor. The provider reads stdin request schema homeboy/agent-task-promotion-apply-request/v1 and writes response schema homeboy/agent-task-promotion-apply-response/v1 with required workspace_path.
--verify<COMMAND>Deterministic verification command that must pass before the cook promotes its work (e.g. --verify "cargo fmt --check"). Required unless --private-verify is given — a cook that cannot verify its work cannot promote it. Runs in the destination worktree. Repeat to require multiple gates; every one must pass. Its output is included in the review evidence
--private-verify<COMMAND>Like --verify, but the command’s output is treated as private: only a pass/fail summary is revealed by default (see --private-gate-reveal). Satisfies the same mandatory-gate requirement as --verify. Use for gates whose logs may contain secrets. Repeatable
--private-gate-reveal<POLICY>How much of a --private-verify gate’s output to reveal: summary-only (default) shows just pass/fail; other policies expose more detail Values: full-evidence, summary-only, redacted, no-detail.
--gate-execution-policy<POLICY>Gate scheduling policy: ordered-fail-fast (default) skips downstream gates after the first failure; continue-all runs every declared gate Values: ordered-fail-fast, continue-all.
--gate-timeout-seconds<SECONDS>Wall-clock timeout, in seconds, for each verification gate command (default 1800 = 30 min). A gate exceeding this fails
--gate-heartbeat-interval-seconds<SECONDS>How often, in seconds, to emit a heartbeat while a gate runs so long gates are not mistaken for a stalled cook (default 5)
--rerun-completed-gatesflagRe-run gates that already recorded a passing result on a previous attempt instead of reusing the recorded pass. Off by default
--gate-environment-mode<MODE>Environment for gate commands: inherit (default) extends the current environment; replace starts from an empty environment plus --gate-env Values: inherit, replace.
--gate-env<NAME=VALUE>Extra environment variable for gate commands, as NAME=VALUE. Repeatable
--gate-env-from<NAME=SOURCE[/PATH]>Preserve a required toolchain setting from the host as NAME=SOURCE or NAME=SOURCE/relative/path. The mapping is retained in gate evidence
--gate-toolchain<COMMAND>Required executable to initialize before provider execution. Its probe is COMMAND --version in the final isolated gate environment. Repeatable
--isolate-gate-home<ISOLATE_GATE_HOME>Run gates with an isolated $HOME so gate side effects do not touch the operator’s home directory (default true) Values: true, false.
--isolate-gate-xdg<ISOLATE_GATE_XDG>Run gates with isolated XDG base directories so gate side effects do not touch the operator’s config/cache/data dirs (default true) Values: true, false.
--max-attempts<N>Maximum cook attempts before giving up. Each attempt re-runs the agent and gates; a later attempt can recover from a transient failure (default 3)
--no-finalizeflagStop after the work is verified but before opening the pull request, leaving the committed change on the worktree branch for manual review or a later agent-task review/finalize
--fullflagReturn the complete cook report, including nested promotion and gate evidence
--base<BRANCH>Base branch the finalized pull request targets and the branch changes are diffed against (default main)
--head<BRANCH>Head branch to push and open the PR from. Defaults to the branch the destination worktree is already on
--title<TEXT>Title for the finalized pull request. Defaults to a title derived from the goal / commit
--commit-message<TEXT>Commit message for the cook’s committed change. Defaults to a message derived from the goal
--protected-branch<BRANCH>Branch names the cook refuses to push to or target directly, as a safety guard. Repeatable; defaults to the standard protected set
--ai-tool<TEXT>AI tool disclosure recorded in the PR’s assistance attribution (default AI-assisted)
--ai-used-for<TEXT>Legacy AI-usage disclosure. The reviewer-facing "Used for" text is now authored by the agent’s review_form.used_for (a self-reflective process description) and validated by the cook loop’s review-form gate; this flag no longer feeds the PR body. Retained only for recipe back-compatibility and defaults empty (no canned platitude)
--require-acceptanceflagRequire a separate durable acceptance verdict before PR finalization
--acceptance-authority<ACCEPTANCE_AUTHORITY>Authority allowed to issue the acceptance verdict
--acceptance-policy<ACCEPTANCE_POLICY>Policy the acceptance authority applies

homeboy agent-task cook-continue

sh
homeboy agent-task cook-continue [OPTIONS] <COOK_OR_ATTEMPT_ID>

Continue a detached Cook from its durable Cook ID or provider attempt ID. The persisted recipe supplies the original prompt, transport, gates, worktree, and disclosure policy

ArgumentRequiredDescription
<COOK_OR_ATTEMPT_ID>yesDurable Cook ID or one of its provider attempt IDs
OptionValueDescription
--fullflagInclude the complete Cook report rather than the compact lifecycle view

homeboy agent-task loop

sh
homeboy agent-task loop <COMMAND>

This command declares no clap help text, so no description can be generated for it.

SubcommandSummary
homeboy agent-task loop defineno help text
homeboy agent-task loop statusno help text
homeboy agent-task loop resumeno help text
homeboy agent-task loop stopno help text

homeboy agent-task loop define

sh
homeboy agent-task loop define [OPTIONS] <SPEC>

This command declares no clap help text, so no description can be generated for it.

ArgumentRequiredDescription
<SPEC>yesno help text
OptionValueDescription
--onflagno help text
--offflagno help text
--revolution-limit<N>no help text
--resumeflagno help text
--dispatch-backend<BACKEND>no help text
--dispatch-selector<PROVIDER_ID>no help text
--dispatch-model<MODEL>no help text
--dispatch-provider-config<JSON>no help text

homeboy agent-task loop status

sh
homeboy agent-task loop status <LOOP_ID>

This command declares no clap help text, so no description can be generated for it.

ArgumentRequiredDescription
<LOOP_ID>yesno help text

homeboy agent-task loop resume

sh
homeboy agent-task loop resume [OPTIONS] <LOOP_ID>

This command declares no clap help text, so no description can be generated for it.

ArgumentRequiredDescription
<LOOP_ID>yesno help text
OptionValueDescription
--revolution-limit<N>no help text
--dispatch-backend<BACKEND>no help text
--dispatch-selector<PROVIDER_ID>no help text
--dispatch-model<MODEL>no help text
--dispatch-provider-config<JSON>no help text

homeboy agent-task loop stop

sh
homeboy agent-task loop stop <LOOP_ID>

This command declares no clap help text, so no description can be generated for it.

ArgumentRequiredDescription
<LOOP_ID>yesno help text

homeboy agent-task run-plan

sh
homeboy agent-task run-plan [OPTIONS]

This command declares no clap help text, so no description can be generated for it.

OptionValueDescription
--plan`<JSON@FILE
--record-run-id<ID>no help text
--timeout-ms<MS>no help text

homeboy agent-task run

sh
homeboy agent-task run [OPTIONS] <RUN_ID>

This command declares no clap help text, so no description can be generated for it.

ArgumentRequiredDescription
<RUN_ID>yesno help text
OptionValueDescription
--timeout-ms<MS>no help text

homeboy agent-task run-next

sh
homeboy agent-task run-next

This command declares no clap help text, so no description can be generated for it.

homeboy agent-task submit

sh
homeboy agent-task submit [OPTIONS]

This command declares no clap help text, so no description can be generated for it.

OptionValueDescription
--plan`<JSON@FILE
--run-id<ID>no help text

homeboy agent-task status

sh
homeboy agent-task status [OPTIONS] <RUN_ID>

This command declares no clap help text, so no description can be generated for it.

ArgumentRequiredDescription
<RUN_ID>yesno help text
OptionValueDescription
--bridgeflagno help text
--since-cursor<CURSOR>no help text
--fullflagno help text
--no-runner-probeflagAnswer from durable controller state only, without reaching the runner

homeboy agent-task list

sh
homeboy agent-task list [OPTIONS]

This command declares no clap help text, so no description can be generated for it.

OptionValueDescription
--limit<N>no help text
--fullflagReturn every matching record. This is intentionally explicit because discovery defaults to a finite agent-facing page

homeboy agent-task active

sh
homeboy agent-task active [OPTIONS]

This command declares no clap help text, so no description can be generated for it.

OptionValueDescription
--limit<N>no help text
--fullflagReturn every matching record. This is intentionally explicit because discovery defaults to a finite agent-facing page
--reconcileflagno help text
--dry-runflagno help text
--applyflagno help text

homeboy agent-task reconcile

sh
homeboy agent-task reconcile [OPTIONS] <RUN_ID>

Preview or apply reconciliation for one durable run

ArgumentRequiredDescription
<RUN_ID>yesno help text
OptionValueDescription
--dry-runflagno help text
--applyflagno help text

homeboy agent-task reconcile-records

sh
homeboy agent-task reconcile-records [OPTIONS]

This command declares no clap help text, so no description can be generated for it.

OptionValueDescription
--dry-runflagno help text

homeboy agent-task latest

sh
homeboy agent-task latest [OPTIONS]

This command declares no clap help text, so no description can be generated for it.

OptionValueDescription
--limit<N>no help text

homeboy agent-task logs

sh
homeboy agent-task logs [OPTIONS] <RUN_ID>

This command declares no clap help text, so no description can be generated for it.

ArgumentRequiredDescription
<RUN_ID>yesno help text
OptionValueDescription
--rawflagInclude unprojected runner transport frames under raw_events for diagnostics

homeboy agent-task artifacts

sh
homeboy agent-task artifacts [OPTIONS] <RUN_ID>

This command declares no clap help text, so no description can be generated for it.

ArgumentRequiredDescription
<RUN_ID>yesno help text
OptionValueDescription
--bridgeflagno help text
--since-cursor<CURSOR>no help text
--fullflagno help text
--no-runner-probeflagAnswer from durable controller state only, without reaching the runner

homeboy agent-task retained-artifacts

sh
homeboy agent-task retained-artifacts <COMMAND>

Discover or attach selected outputs retained in a terminal Lab Cook workspace

SubcommandSummary
homeboy agent-task retained-artifacts discoverResolve the retained workspace and print bounded, run-ID-only attach guidance
homeboy agent-task retained-artifacts attachAttach one repository-relative file or directory from the retained workspace

homeboy agent-task retained-artifacts discover

sh
homeboy agent-task retained-artifacts discover <RUN_ID>

Resolve the retained workspace and print bounded, run-ID-only attach guidance

ArgumentRequiredDescription
<RUN_ID>yesno help text

homeboy agent-task retained-artifacts attach

sh
homeboy agent-task retained-artifacts attach [OPTIONS] <RUN_ID>

Attach one repository-relative file or directory from the retained workspace

ArgumentRequiredDescription
<RUN_ID>yesno help text
OptionValueDescription
--path<PATH>Repository-relative path below the retained workspace
--name<NAME>Durable artifact name to record on the owning run

homeboy agent-task evidence

sh
homeboy agent-task evidence [OPTIONS] <RUN_ID>

This command declares no clap help text, so no description can be generated for it.

ArgumentRequiredDescription
<RUN_ID>yesno help text
OptionValueDescription
--kind<KIND>no help text
--task<TASK_ID>no help text
--failure-onlyflagno help text
--fullflagReturn every matching evidence record rather than the bounded preview

homeboy agent-task diagnose

sh
homeboy agent-task diagnose [OPTIONS] <RUN_ID>

This command declares no clap help text, so no description can be generated for it.

ArgumentRequiredDescription
<RUN_ID>yesno help text
OptionValueDescription
--fullflagHydrate every available evidence summary rather than the bounded preview

homeboy agent-task runtime-recover

sh
homeboy agent-task runtime-recover [OPTIONS] <RUN_ID>

Recover a missing or corrupted immutable controller runtime pin

ArgumentRequiredDescription
<RUN_ID>yesDurable run whose exact controller executable should be rematerialized
OptionValueDescription
--source<PATH>Trusted source checkout used to rebuild the recorded runtime revision
--artifact<PATH>Exact prebuilt controller executable. Its hash and self identity must match the durable pin

homeboy agent-task runtime-validate

sh
homeboy agent-task runtime-validate <RUN_ID>

Validate controller runtime eligibility without executing provider work

ArgumentRequiredDescription
<RUN_ID>yesDurable run to validate without executing its provider lifecycle

homeboy agent-task replay-provider-boundary

sh
homeboy agent-task replay-provider-boundary [OPTIONS] <RUN_ID>

This command declares no clap help text, so no description can be generated for it.

ArgumentRequiredDescription
<RUN_ID>yesno help text
OptionValueDescription
--task<TASK_ID>no help text

homeboy agent-task cancel

sh
homeboy agent-task cancel [OPTIONS] <RUN_ID>

This command declares no clap help text, so no description can be generated for it.

ArgumentRequiredDescription
<RUN_ID>yesno help text
OptionValueDescription
--reason<TEXT>no help text

homeboy agent-task resume

sh
homeboy agent-task resume [OPTIONS] <RUN_ID>

This command declares no clap help text, so no description can be generated for it.

ArgumentRequiredDescription
<RUN_ID>yesno help text
OptionValueDescription
--bridgeflagno help text
--since-cursor<CURSOR>no help text
--fullflagno help text
--no-runner-probeflagAnswer from durable controller state only, without reaching the runner

homeboy agent-task retry

sh
homeboy agent-task retry [OPTIONS] <RUN_ID>

This command declares no clap help text, so no description can be generated for it.

ArgumentRequiredDescription
<RUN_ID>yesno help text
OptionValueDescription
--new-run-id<ID>no help text
--runflagno help text
--forceflagPermit a new retry after every prior retry in this lineage is terminal

homeboy agent-task fanout

sh
homeboy agent-task fanout <COMMAND>

This command declares no clap help text, so no description can be generated for it.

SubcommandSummary
homeboy agent-task fanout cook-batchCook a wave of independent tasks, one child cook per issue
homeboy agent-task fanout planno help text
homeboy agent-task fanout submitno help text
homeboy agent-task fanout submit-batchno help text
homeboy agent-task fanout statusno help text
homeboy agent-task fanout resumeResume a durable fanout batch after coordinator loss: idempotently harvest terminal children through gates, commit, push, and PR finalization
homeboy agent-task fanout artifactsno help text
homeboy agent-task fanout run-planno help text

homeboy agent-task fanout cook-batch

sh
homeboy agent-task fanout cook-batch [OPTIONS] <ISSUE_URL>...

Cook a wave of independent tasks, one child cook per issue.

Requires at least one deterministic gate: pass --verify or --private-verify. The gate is not optional — a child cook that cannot verify its work cannot promote it (#9838).

ArgumentRequiredDescription
<ISSUE_URL>...yesno help text
OptionValueDescription
--repo<REPO>no help text
--from<REF>no help text
--base<BRANCH>no help text
--branch-prefix<PREFIX>no help text
--fanout-id<ID>no help text
--prompt-template<TEXT>no help text
--backend<BACKEND>no help text
--selector<PROVIDER_ID>no help text
--model<MODEL>no help text
--provider-profile<PROFILE>no help text
--secret-env<ENV>no help text
--provider-config<JSON>no help text
--verify<COMMAND>Deterministic verification command that must pass before the cook promotes its work (e.g. --verify "cargo fmt --check"). Required unless --private-verify is given — a cook that cannot verify its work cannot promote it. Runs in the destination worktree. Repeat to require multiple gates; every one must pass. Its output is included in the review evidence
--private-verify<COMMAND>Like --verify, but the command’s output is treated as private: only a pass/fail summary is revealed by default (see --private-gate-reveal). Satisfies the same mandatory-gate requirement as --verify. Use for gates whose logs may contain secrets. Repeatable
--private-gate-reveal<POLICY>How much of a --private-verify gate’s output to reveal: summary-only (default) shows just pass/fail; other policies expose more detail Values: full-evidence, summary-only, redacted, no-detail.
--gate-execution-policy<POLICY>Gate scheduling policy: ordered-fail-fast (default) skips downstream gates after the first failure; continue-all runs every declared gate Values: ordered-fail-fast, continue-all.
--gate-timeout-seconds<SECONDS>Wall-clock timeout, in seconds, for each verification gate command (default 1800 = 30 min). A gate exceeding this fails
--gate-heartbeat-interval-seconds<SECONDS>How often, in seconds, to emit a heartbeat while a gate runs so long gates are not mistaken for a stalled cook (default 5)
--rerun-completed-gatesflagRe-run gates that already recorded a passing result on a previous attempt instead of reusing the recorded pass. Off by default
--gate-environment-mode<MODE>Environment for gate commands: inherit (default) extends the current environment; replace starts from an empty environment plus --gate-env Values: inherit, replace.
--gate-env<NAME=VALUE>Extra environment variable for gate commands, as NAME=VALUE. Repeatable
--gate-env-from<NAME=SOURCE[/PATH]>Preserve a required toolchain setting from the host as NAME=SOURCE or NAME=SOURCE/relative/path. The mapping is retained in gate evidence
--gate-toolchain<COMMAND>Required executable to initialize before provider execution. Its probe is COMMAND --version in the final isolated gate environment. Repeatable
--isolate-gate-home<ISOLATE_GATE_HOME>Run gates with an isolated $HOME so gate side effects do not touch the operator’s home directory (default true) Values: true, false.
--isolate-gate-xdg<ISOLATE_GATE_XDG>Run gates with isolated XDG base directories so gate side effects do not touch the operator’s config/cache/data dirs (default true) Values: true, false.
--dry-runflagno help text
--run-planflagno help text

homeboy agent-task fanout plan

sh
homeboy agent-task fanout plan [OPTIONS]

This command declares no clap help text, so no description can be generated for it.

OptionValueDescription
--input<SPEC>no help text
--fanout-id<ID>no help text
--backend<BACKEND>no help text
--selector<PROVIDER_ID>no help text
--model<MODEL>no help text

homeboy agent-task fanout submit

sh
homeboy agent-task fanout submit [OPTIONS]

This command declares no clap help text, so no description can be generated for it.

OptionValueDescription
--input<SPEC>no help text
--fanout-id<ID>no help text
--backend<BACKEND>no help text
--selector<PROVIDER_ID>no help text
--model<MODEL>no help text
--run-id<ID>no help text

homeboy agent-task fanout submit-batch

sh
homeboy agent-task fanout submit-batch [OPTIONS]

This command declares no clap help text, so no description can be generated for it.

OptionValueDescription
--input<SPEC>no help text
--fanout-id<ID>no help text
--backend<BACKEND>no help text
--selector<PROVIDER_ID>no help text
--model<MODEL>no help text
--batch-id<ID>no help text

homeboy agent-task fanout status

sh
homeboy agent-task fanout status <BATCH_ID>

This command declares no clap help text, so no description can be generated for it.

ArgumentRequiredDescription
<BATCH_ID>yesno help text

homeboy agent-task fanout resume

sh
homeboy agent-task fanout resume <BATCH_ID>

Resume a durable fanout batch after coordinator loss: idempotently harvest terminal children through gates, commit, push, and PR finalization

ArgumentRequiredDescription
<BATCH_ID>yesno help text

homeboy agent-task fanout artifacts

sh
homeboy agent-task fanout artifacts <BATCH_ID>

This command declares no clap help text, so no description can be generated for it.

ArgumentRequiredDescription
<BATCH_ID>yesno help text

homeboy agent-task fanout run-plan

sh
homeboy agent-task fanout run-plan [OPTIONS]

This command declares no clap help text, so no description can be generated for it.

OptionValueDescription
--input<SPEC>no help text
--fanout-id<ID>no help text
--backend<BACKEND>no help text
--selector<PROVIDER_ID>no help text
--model<MODEL>no help text
--record-run-id<ID>no help text

homeboy agent-task review

sh
homeboy agent-task review [OPTIONS] <RUN_ID>

This command declares no clap help text, so no description can be generated for it.

ArgumentRequiredDescription
<RUN_ID>yesno help text
OptionValueDescription
--to-worktree<HANDLE>no help text
--provider-command<COMMAND>Deprecated promotion apply-provider command string. Migrate --provider-command 'provider --flag value' to --provider-argv provider --provider-argv --flag --provider-argv value; argv preserves exact arguments without shell splitting. The provider reads stdin request schema homeboy/agent-task-promotion-apply-request/v1 and writes response schema homeboy/agent-task-promotion-apply-response/v1 with workspace_path.
--provider-argv<ARG>Promotion-only apply-provider invocation argument. Repeat once per exact argv element: the first is the executable and later values are its arguments; values are never shell-split. This cannot select an executor. The provider reads stdin request schema homeboy/agent-task-promotion-apply-request/v1 and writes response schema homeboy/agent-task-promotion-apply-response/v1 with required workspace_path.

homeboy agent-task promote

sh
homeboy agent-task promote [OPTIONS] <SOURCE>

This command declares no clap help text, so no description can be generated for it.

ArgumentRequiredDescription
<SOURCE>yesno help text
OptionValueDescription
--to-worktree<HANDLE>no help text
--base<BRANCH>Declared base branch resolved immediately before promotion gates run
--provider-command<COMMAND>Deprecated promotion apply-provider command string. Migrate --provider-command 'provider --flag value' to --provider-argv provider --provider-argv --flag --provider-argv value; argv preserves exact arguments without shell splitting. The provider reads stdin request schema homeboy/agent-task-promotion-apply-request/v1 and writes response schema homeboy/agent-task-promotion-apply-response/v1 with workspace_path.
--provider-argv<ARG>Promotion-only apply-provider invocation argument. Repeat once per exact argv element: the first is the executable and later values are its arguments; values are never shell-split. This cannot select an executor. The provider reads stdin request schema homeboy/agent-task-promotion-apply-request/v1 and writes response schema homeboy/agent-task-promotion-apply-response/v1 with required workspace_path.
--task-id<TASK_ID>no help text
--artifact-id<ARTIFACT_ID>no help text
--dry-runflagno help text
--verify<COMMAND>Deterministic verification command that must pass before the cook promotes its work (e.g. --verify "cargo fmt --check"). Required unless --private-verify is given — a cook that cannot verify its work cannot promote it. Runs in the destination worktree. Repeat to require multiple gates; every one must pass. Its output is included in the review evidence
--private-verify<COMMAND>Like --verify, but the command’s output is treated as private: only a pass/fail summary is revealed by default (see --private-gate-reveal). Satisfies the same mandatory-gate requirement as --verify. Use for gates whose logs may contain secrets. Repeatable
--private-gate-reveal<POLICY>How much of a --private-verify gate’s output to reveal: summary-only (default) shows just pass/fail; other policies expose more detail Values: full-evidence, summary-only, redacted, no-detail.
--gate-execution-policy<POLICY>Gate scheduling policy: ordered-fail-fast (default) skips downstream gates after the first failure; continue-all runs every declared gate Values: ordered-fail-fast, continue-all.
--gate-timeout-seconds<SECONDS>Wall-clock timeout, in seconds, for each verification gate command (default 1800 = 30 min). A gate exceeding this fails
--gate-heartbeat-interval-seconds<SECONDS>How often, in seconds, to emit a heartbeat while a gate runs so long gates are not mistaken for a stalled cook (default 5)
--rerun-completed-gatesflagRe-run gates that already recorded a passing result on a previous attempt instead of reusing the recorded pass. Off by default
--gate-environment-mode<MODE>Environment for gate commands: inherit (default) extends the current environment; replace starts from an empty environment plus --gate-env Values: inherit, replace.
--gate-env<NAME=VALUE>Extra environment variable for gate commands, as NAME=VALUE. Repeatable
--gate-env-from<NAME=SOURCE[/PATH]>Preserve a required toolchain setting from the host as NAME=SOURCE or NAME=SOURCE/relative/path. The mapping is retained in gate evidence
--gate-toolchain<COMMAND>Required executable to initialize before provider execution. Its probe is COMMAND --version in the final isolated gate environment. Repeatable
--isolate-gate-home<ISOLATE_GATE_HOME>Run gates with an isolated $HOME so gate side effects do not touch the operator’s home directory (default true) Values: true, false.
--isolate-gate-xdg<ISOLATE_GATE_XDG>Run gates with isolated XDG base directories so gate side effects do not touch the operator’s config/cache/data dirs (default true) Values: true, false.

homeboy agent-task adopt

sh
homeboy agent-task adopt [OPTIONS] <RUN_OR_COOK_ID>

Adopt an immutable commit candidate through a tracked cook’s normal gates and finalization

ArgumentRequiredDescription
<RUN_OR_COOK_ID>yesExisting durable run id or cook id whose recipe owns the candidate lifecycle
OptionValueDescription
--attempt<N>Select an exact durable attempt from the Cook recipe. Required when attempts use different policies
--candidate-ref<SHA>Immutable commit revision in the recorded source worktree
--ai-model<MODEL>Concrete model that prepared the externally supplied candidate
--replace-interruptedflagReplace a stale interrupted adoption while retaining its lifecycle evidence
--fullflagReturn the complete cook adoption report, including nested gate evidence

homeboy agent-task finalize-pr

sh
homeboy agent-task finalize-pr [OPTIONS]

This command declares no clap help text, so no description can be generated for it.

OptionValueDescription
--recover<RUN_OR_COOK_ID>Hydrate finalization from a durable Cook recipe and its applied promotion
--run-id<ID>no help text
--path<PATH>no help text
--base<BRANCH>no help text
--verified-base-sha<SHA>Immutable base commit SHA recorded before the declared verification gates ran
--head<BRANCH>no help text
--title<TEXT>no help text
--commit-message<TEXT>no help text
--attempt-summary<TEXT>Attempt summary to include in the PR body
--source-ref<REF>Source tracker/reference URL or identifier. Repeatable
--artifact-ref<REF>Artifact/evidence URL, path, or identifier. Repeatable
--ai-tool<TEXT>AI tool disclosure line for the PR body
--ai-model<MODEL>Actual model identifier for AI disclosure. Finalization requires a recorded model
--related-finding-id<ID>Source finding id shared by sibling generated PRs
--source-packet-id<ID>Source validation packet id shared by sibling generated PRs
--change-kind<KIND>Generated change kind, e.g. evidence-only, runtime-fix, or test-only
--supersedes<REF>Generated PR or artifact this PR supersedes. Repeatable
--depends-on<REF>Generated PR or artifact this PR depends on. Repeatable
--targeted-check-run<COMMAND>Targeted verification command that ran before finalization. Repeatable
--targeted-checks-unavailable<TEXT>Exact backend limitation when targeted checks could not be run
--ci-expected<CHECK>CI check expected to run after push. Repeatable
--manual-reviewer-check<TEXT>Manual reviewer verification requested when targeted checks/CI do not cover behavior
--why-not-broader-than-packet<TEXT>Runtime-fix evidence bound for generated predicates/semantics
--evidence-discriminator<TEXT>Evidence-specific discriminator preserved by the runtime fix. Repeatable
--nearby-contract-preserved<TEXT>Nearby predicate/contract preserved by the runtime fix. Repeatable
--changed-public-contract<ID=>SUMMARY>Declared changed public contract as ID=>SUMMARY. Requires the complete compatibility/external-usage evidence bundle below
--compatibility-impact<TEXT>Compatibility impact for declared public contracts
--external-consumer-impact<TEXT>External-consumer impact for declared public contracts
--external-usage-status<STATUS>External usage evidence status: completed or unavailable_manual_review
--external-usage-source<TEXT>Source used for external usage evidence
--external-usage-limitations<TEXT>Limitations of the external usage evidence or manual review
--external-usage-url<URL>Reviewer-resolvable HTTPS URL for external usage evidence
--gate-result<NAME=STATUS[:DETAIL]>no help text
--changed-file<PATH>no help text
--protected-branch<BRANCH>no help text
--ai-used-for<TEXT>no help text
--summary<TEXT>no help text
--what-changed<TEXT>no help text
--test-step<COMMAND=>EXPECTED>Reviewer test step. Strict shape: COMMAND=>EXPECTED
--compatibility<TEXT>no help text
--closes<ISSUE_REF>Closing issue reference: #NUMBER, OWNER/REPO#NUMBER, or a github.com issue URL
--relates-to<ISSUE_REF>Related issue reference: #NUMBER, OWNER/REPO#NUMBER, or a github.com issue URL
--review-override<TARGET=VALUE@PROVENANCE>no help text
--preflightflagValidate the complete hydrated dossier and candidate without publishing
--manual-finalizationflagno help text

homeboy agent-task accept

sh
homeboy agent-task accept [OPTIONS] <RUN_ID>

Record an independent, durable acceptance verdict for a candidate

ArgumentRequiredDescription
<RUN_ID>yesno help text
OptionValueDescription
--verdict<VERDICT>no help text Values: accepted, rejected.
--token<TOKEN>Opaque credential consumed by the configured acceptance verifier
--evidence-ref<EVIDENCE_REFS>no help text

homeboy agent-task gate-feedback

sh
homeboy agent-task gate-feedback [OPTIONS]

This command declares no clap help text, so no description can be generated for it.

OptionValueDescription
--promotion`<JSON@FILE
--source-task`<JSON@FILE
--attempt<N>no help text
--max-attempts<N>no help text
--source-run-id<ID>no help text
--current-diff<SPEC>no help text

homeboy agent-task providers

sh
homeboy agent-task providers [OPTIONS]

This command declares no clap help text, so no description can be generated for it.

OptionValueDescription
--backend<BACKEND>no help text
--selector<PROVIDER_ID>no help text
--runtime<RUNTIME>Restrict results to the runtime that owns the provider
--status<STATUS>Restrict results to default or available providers
--secret-env<ENV>no help text
--validate-readinessflagno help text
--refreshflagno help text
--catalogflagReturn the full multi-backend catalog even when --backend is set. Without this, --backend X filters the presentation to X so the output stays within caller display limits (#9654)
--fullflagReturn the complete provider declarations and discovery diagnostics

homeboy agent-task prompts

sh
homeboy agent-task prompts <COMMAND>

This command declares no clap help text, so no description can be generated for it.

SubcommandSummary
homeboy agent-task prompts saveSave a markdown prompt in Homeboy’s agent-task prompt store
homeboy agent-task prompts listList stored agent-task prompts
homeboy agent-task prompts showShow a stored agent-task prompt
homeboy agent-task prompts removeRemove a stored agent-task prompt

homeboy agent-task prompts save

sh
homeboy agent-task prompts save [OPTIONS] <NAME>

Save a markdown prompt in Homeboy’s agent-task prompt store

ArgumentRequiredDescription
<NAME>yesStable prompt name. Unsafe path characters are normalized for storage
OptionValueDescription
--input<PROMPT>Prompt markdown content, @file, or – for stdin

homeboy agent-task prompts list

sh
homeboy agent-task prompts list

List stored agent-task prompts

homeboy agent-task prompts show

sh
homeboy agent-task prompts show <NAME>

Show a stored agent-task prompt

ArgumentRequiredDescription
<NAME>yesStored prompt name or id

homeboy agent-task prompts remove

sh
homeboy agent-task prompts remove <NAME>

Remove a stored agent-task prompt

ArgumentRequiredDescription
<NAME>yesStored prompt name or id

homeboy agent-task contract

sh
homeboy agent-task contract [OPTIONS]

This command declares no clap help text, so no description can be generated for it.

OptionValueDescription
--format<FORMAT>no help text Values: json.

homeboy agent-task compile-loop

sh
homeboy agent-task compile-loop [OPTIONS]

This command declares no clap help text, so no description can be generated for it.

OptionValueDescription
--definition<SPEC>no help text

homeboy agent-task auth

sh
homeboy agent-task auth <COMMAND>

This command declares no clap help text, so no description can be generated for it.

SubcommandSummary
homeboy agent-task auth statusShow redacted readiness for provider secret environment variables
homeboy agent-task auth set-keychainStore a provider secret in the OS keychain and map it to a required env name
homeboy agent-task auth set-configStore a provider secret in Homeboy global config and map it to a required env name
homeboy agent-task auth set-keychain-bundleStore a JSON secret bundle in one OS keychain item
homeboy agent-task auth map-envMap a required provider env name to another process env var
homeboy agent-task auth map-keychain-bundleMap a required provider env name to a field in a JSON keychain bundle
homeboy agent-task auth removeRemove a provider secret source mapping

homeboy agent-task auth status

sh
homeboy agent-task auth status [OPTIONS]

Show redacted readiness for provider secret environment variables

OptionValueDescription
--backend<BACKEND>Executor backend whose required secrets to report. Defaults to the same backend cook/dispatch would use when omitted
--selector<PROVIDER_ID>Provider id to disambiguate when more than one provider exists for the backend
--secret-env<ENV>Secret environment variable name to check without exposing its value. Repeatable. When omitted, the selected backend’s required secrets are used

homeboy agent-task auth set-keychain

sh
homeboy agent-task auth set-keychain [OPTIONS] <ENV> [VALUE]

Store a provider secret in the OS keychain and map it to a required env name

ArgumentRequiredDescription
<ENV>yesRequired provider environment variable name to satisfy
[VALUE]noSecret value. Omit to prompt securely
OptionValueDescription
--value-stdinflagRead the secret value from stdin
--scope<SCOPE>Keychain scope. Defaults to agent-task
--name<NAME>Keychain entry name. Defaults to ENV

homeboy agent-task auth set-config

sh
homeboy agent-task auth set-config [OPTIONS] <ENV> [VALUE]

Store a provider secret in Homeboy global config and map it to a required env name

ArgumentRequiredDescription
<ENV>yesRequired provider environment variable name to satisfy
[VALUE]noSecret value. Omit to prompt securely
OptionValueDescription
--value-stdinflagRead the secret value from stdin

homeboy agent-task auth set-keychain-bundle

sh
homeboy agent-task auth set-keychain-bundle [OPTIONS] <BUNDLE> [JSON]

Store a JSON secret bundle in one OS keychain item

ArgumentRequiredDescription
<BUNDLE>yesLogical bundle id to store
[JSON]noJSON bundle value. Omit to prompt securely
OptionValueDescription
--value-stdinflagRead the JSON bundle value from stdin
--scope<SCOPE>Keychain scope. Defaults to agent-task
--name<NAME>Keychain entry name. Defaults to BUNDLE

homeboy agent-task auth map-env

sh
homeboy agent-task auth map-env [OPTIONS] <ENV>

Map a required provider env name to another process env var

ArgumentRequiredDescription
<ENV>yesRequired provider environment variable name to satisfy
OptionValueDescription
--from<ENV>Source process environment variable. Defaults to ENV

homeboy agent-task auth map-keychain-bundle

sh
homeboy agent-task auth map-keychain-bundle [OPTIONS] <ENV>

Map a required provider env name to a field in a JSON keychain bundle

ArgumentRequiredDescription
<ENV>yesRequired provider environment variable name to satisfy
OptionValueDescription
--bundle<BUNDLE>Logical bundle id to read
--field<FIELD>Field path inside the JSON bundle, using dots for nested objects
--scope<SCOPE>Keychain scope. Defaults to agent-task
--name<NAME>Keychain entry name. Defaults to BUNDLE

homeboy agent-task auth remove

sh
homeboy agent-task auth remove [OPTIONS] <ENV>

Remove a provider secret source mapping

ArgumentRequiredDescription
<ENV>yesRequired provider environment variable name whose mapping should be removed
OptionValueDescription
--keychainflagAlso remove the mapped keychain entry when the mapping points at keychain

homeboy agent-task controller

sh
homeboy agent-task controller <COMMAND>

This command declares no clap help text, so no description can be generated for it.

SubcommandSummary
homeboy agent-task controller initCreate a durable loop controller record
homeboy agent-task controller from-specInitialize or resume a durable loop controller from a repo-authored JSON spec
homeboy agent-task controller run-from-specMaterialize, initialize, and run a bounded controller loop from a repo-authored JSON spec
homeboy agent-task controller materializeMaterialize a repo-authored loop spec with explicit run inputs
homeboy agent-task controller validate-proofValidate a proof, materialized spec, or controller record for deterministic handoff
homeboy agent-task controller planCompile a controller spec into a dry Homeboy plan without writing state
homeboy agent-task controller statusRead a durable loop controller record
homeboy agent-task controller diagnoseRender the controller failure tree for failed child actions
homeboy agent-task controller listList durable loop controller records
homeboy agent-task controller eventsApply a generic external controller event
homeboy agent-task controller apply-eventApply an external event and resume matching waits
homeboy agent-task controller run-nextClaim and execute the next pending controller action
homeboy agent-task controller runClaim and execute one pending controller action
homeboy agent-task controller resumeExecute pending controller actions until no executable action remains
homeboy agent-task controller mark-human-readyMark a tracked entity as human-ready work
homeboy agent-task controller proofRun a one-command end-to-end controller proof from a named profile + runner

homeboy agent-task controller init

sh
homeboy agent-task controller init [OPTIONS] <LOOP_ID>

Create a durable loop controller record

ArgumentRequiredDescription
<LOOP_ID>yesDurable loop id. Unsafe path characters are normalized for storage
OptionValueDescription
--phase<PHASE>Initial controller phase
--config-version<VERSION>Declared graph/config version for resume compatibility

homeboy agent-task controller from-spec

sh
homeboy agent-task controller from-spec [OPTIONS] <SPEC>

Initialize or resume a durable loop controller from a repo-authored JSON spec.

With a configured default Lab runner, –resume uses automatic Lab offload unless local execution is explicitly forced.

ArgumentRequiredDescription
<SPEC>yesRepo loop spec JSON, @file, or – for stdin
OptionValueDescription
--resumeflagExecute pending actions after applying the spec
--inputs<JSON>Explicit controller run inputs JSON, @file, or – for stdin. Supports inputs and metadata objects
--policy-result<JSON>Declarative policy result JSON, @file, or – for stdin. Repeatable
--max-actions<N>Maximum controller actions to execute when –resume is supplied
--reconcile-staleflagOn –resume, automatically reset stale persisted controller state and re-create it from this spec
--replaceflagOn –resume, discard stale persisted controller state and re-create it from this spec
--forkflagOn –resume, apply this spec under a derived fork loop id, leaving the original untouched
--resume-existingflagOn –resume, accept stale/mismatched persisted state and resume the existing controller as-is
--doctorflagCompile and preflight generic controller prerequisites without writing state
--dispatch-backend<BACKEND>Executor backend to use for controller-spawned dispatch actions when the action omits one
--dispatch-selector<PROVIDER_ID>Extension-provider selector: the Homeboy executor provider id (e.g. sample.executor-provider) that runs controller-spawned dispatch actions when the action omits one. This is not model/runtime provider configuration; pass runtime-specific values in –dispatch-provider-config. Run homeboy agent-task providers for valid ids
--dispatch-model<MODEL>Model override to use for controller-spawned dispatch actions when the action omits one
--dispatch-provider-config<JSON>Agent/model provider config (JSON, @file, or -): the nested AI runtime/provider/model the selected executor uses for controller-spawned dispatch actions when the action omits one. Put runtime-specific provider selection here, not in –dispatch-selector

homeboy agent-task controller run-from-spec

sh
homeboy agent-task controller run-from-spec [OPTIONS] <SPEC>

Materialize, initialize, and run a bounded controller loop from a repo-authored JSON spec.

With a configured default Lab runner, this uses automatic Lab offload unless local execution is explicitly forced.

ArgumentRequiredDescription
<SPEC>yesRepo loop spec JSON, @file, -, or a generator manifest that writes a spec file
OptionValueDescription
--inputs<JSON>Explicit run inputs JSON, @file, or – for stdin. Supports inputs and metadata objects
--policy-result<JSON>Declarative policy result JSON, @file, or – for stdin. Repeatable
--max-actions<N>Maximum controller actions to execute before returning a bounded partial result
--reconcile-staleflagOne-flag safe proof-run mode: automatically reset stale persisted controller state and re-derive isolated run-scoped state from this spec, with no manual state cleanup. Use this for proof/rerun workflows when the persisted spec fingerprint conflicts with the requested spec
--replaceflagDiscard stale persisted controller state and re-create it from this spec before running
--forkflagApply this spec under a derived fork loop id, leaving the original controller untouched
--resume-existingflagAccept stale/mismatched persisted state and resume the existing controller as-is
--dispatch-backend<BACKEND>Executor backend to use for controller-spawned dispatch actions when the action omits one
--dispatch-selector<PROVIDER_ID>Extension-provider selector: the Homeboy executor provider id (e.g. sample.executor-provider) that runs controller-spawned dispatch actions when the action omits one. This is not model/runtime provider configuration; pass runtime-specific values in –dispatch-provider-config. Run homeboy agent-task providers for valid ids
--dispatch-model<MODEL>Model override to use for controller-spawned dispatch actions when the action omits one
--dispatch-provider-config<JSON>Agent/model provider config (JSON, @file, or -): the nested AI runtime/provider/model the selected executor uses for controller-spawned dispatch actions when the action omits one. Put runtime-specific provider selection here, not in –dispatch-selector

homeboy agent-task controller materialize

sh
homeboy agent-task controller materialize [OPTIONS] <SPEC>

Materialize a repo-authored loop spec with explicit run inputs.

With a configured default Lab runner, this uses automatic Lab offload unless local execution is explicitly forced.

ArgumentRequiredDescription
<SPEC>yesRepo loop spec JSON, @file, -, or a generator manifest that writes a spec file
OptionValueDescription
--inputs<JSON>Explicit run inputs JSON, @file, or – for stdin. Supports inputs and metadata objects
--policy-result<JSON>Declarative policy result JSON, @file, or – for stdin. Repeatable

homeboy agent-task controller validate-proof

sh
homeboy agent-task controller validate-proof <JSON>

Validate a proof, materialized spec, or controller record for deterministic handoff

ArgumentRequiredDescription
<JSON>yesProof JSON, materialize output JSON, controller record JSON, @file, or – for stdin

homeboy agent-task controller plan

sh
homeboy agent-task controller plan <SPEC>

Compile a controller spec into a dry Homeboy plan without writing state

ArgumentRequiredDescription
<SPEC>yesController spec JSON, @file, or – for stdin

homeboy agent-task controller status

sh
homeboy agent-task controller status [OPTIONS] <LOOP_ID>

Read a durable loop controller record

ArgumentRequiredDescription
<LOOP_ID>yesDurable loop id returned by agent-task controller init
OptionValueDescription
--spec<SPEC>Optional repo loop spec JSON, @file, or – to compare against persisted controller state
--dispatch-backend<BACKEND>Executor backend to use for controller-spawned dispatch actions when the action omits one
--dispatch-selector<PROVIDER_ID>Extension-provider selector: the Homeboy executor provider id (e.g. sample.executor-provider) that runs controller-spawned dispatch actions when the action omits one. This is not model/runtime provider configuration; pass runtime-specific values in –dispatch-provider-config. Run homeboy agent-task providers for valid ids
--dispatch-model<MODEL>Model override to use for controller-spawned dispatch actions when the action omits one
--dispatch-provider-config<JSON>Agent/model provider config (JSON, @file, or -): the nested AI runtime/provider/model the selected executor uses for controller-spawned dispatch actions when the action omits one. Put runtime-specific provider selection here, not in –dispatch-selector

homeboy agent-task controller diagnose

sh
homeboy agent-task controller diagnose [OPTIONS] <LOOP_ID>

Render the controller failure tree for failed child actions

ArgumentRequiredDescription
<LOOP_ID>yesDurable loop id returned by agent-task controller init
OptionValueDescription
--spec<SPEC>Optional repo loop spec JSON, @file, or – to compare against persisted controller state
--dispatch-backend<BACKEND>Executor backend to use for controller-spawned dispatch actions when the action omits one
--dispatch-selector<PROVIDER_ID>Extension-provider selector: the Homeboy executor provider id (e.g. sample.executor-provider) that runs controller-spawned dispatch actions when the action omits one. This is not model/runtime provider configuration; pass runtime-specific values in –dispatch-provider-config. Run homeboy agent-task providers for valid ids
--dispatch-model<MODEL>Model override to use for controller-spawned dispatch actions when the action omits one
--dispatch-provider-config<JSON>Agent/model provider config (JSON, @file, or -): the nested AI runtime/provider/model the selected executor uses for controller-spawned dispatch actions when the action omits one. Put runtime-specific provider selection here, not in –dispatch-selector

homeboy agent-task controller list

sh
homeboy agent-task controller list

List durable loop controller records

homeboy agent-task controller events

sh
homeboy agent-task controller events [OPTIONS] <LOOP_ID>

Apply a generic external controller event

ArgumentRequiredDescription
<LOOP_ID>yesDurable loop id returned by agent-task controller init
OptionValueDescription
--event-type<TYPE>External event type, for example github.pr.merged or task.completed
--event-id<ID>Stable event id. Generated from the loop history length when omitted
--event-key<KEY>Optional deterministic event key, such as repo#pr or a check-suite id
--entity-id<ID>Optional target entity id for wait matching and lineage
--payload<JSON>Event payload JSON, @file, or – for stdin. May contain a policy object to evaluate

homeboy agent-task controller apply-event

sh
homeboy agent-task controller apply-event [OPTIONS] <LOOP_ID>

Apply an external event and resume matching waits

ArgumentRequiredDescription
<LOOP_ID>yesDurable loop id returned by agent-task controller init
OptionValueDescription
--event-type<TYPE>External event type, for example github.pr.merged or task.completed
--event-id<ID>Stable event id. Generated from the loop history length when omitted
--event-key<KEY>Optional deterministic event key, such as repo#pr or a check-suite id
--entity-id<ID>Optional target entity id for wait matching and lineage
--payload<JSON>Event payload JSON, @file, or – for stdin. May contain a policy object to evaluate

homeboy agent-task controller run-next

sh
homeboy agent-task controller run-next [OPTIONS] <LOOP_ID>

Claim and execute the next pending controller action

ArgumentRequiredDescription
<LOOP_ID>yesDurable loop id returned by agent-task controller init
OptionValueDescription
--dispatch-backend<BACKEND>Executor backend to use for controller-spawned dispatch actions when the action omits one
--dispatch-selector<PROVIDER_ID>Extension-provider selector: the Homeboy executor provider id (e.g. sample.executor-provider) that runs controller-spawned dispatch actions when the action omits one. This is not model/runtime provider configuration; pass runtime-specific values in –dispatch-provider-config. Run homeboy agent-task providers for valid ids
--dispatch-model<MODEL>Model override to use for controller-spawned dispatch actions when the action omits one
--dispatch-provider-config<JSON>Agent/model provider config (JSON, @file, or -): the nested AI runtime/provider/model the selected executor uses for controller-spawned dispatch actions when the action omits one. Put runtime-specific provider selection here, not in –dispatch-selector

homeboy agent-task controller run

sh
homeboy agent-task controller run [OPTIONS] <LOOP_ID>

Claim and execute one pending controller action

ArgumentRequiredDescription
<LOOP_ID>yesDurable loop id returned by agent-task controller init
OptionValueDescription
--action-id<ID>Pending controller action id to execute
--dispatch-backend<BACKEND>Executor backend to use for controller-spawned dispatch actions when the action omits one
--dispatch-selector<PROVIDER_ID>Extension-provider selector: the Homeboy executor provider id (e.g. sample.executor-provider) that runs controller-spawned dispatch actions when the action omits one. This is not model/runtime provider configuration; pass runtime-specific values in –dispatch-provider-config. Run homeboy agent-task providers for valid ids
--dispatch-model<MODEL>Model override to use for controller-spawned dispatch actions when the action omits one
--dispatch-provider-config<JSON>Agent/model provider config (JSON, @file, or -): the nested AI runtime/provider/model the selected executor uses for controller-spawned dispatch actions when the action omits one. Put runtime-specific provider selection here, not in –dispatch-selector

homeboy agent-task controller resume

sh
homeboy agent-task controller resume [OPTIONS] <LOOP_ID>

Execute pending controller actions until no executable action remains

ArgumentRequiredDescription
<LOOP_ID>yesDurable loop id returned by agent-task controller init
OptionValueDescription
--dispatch-backend<BACKEND>Executor backend to use for controller-spawned dispatch actions when the action omits one
--dispatch-selector<PROVIDER_ID>Extension-provider selector: the Homeboy executor provider id (e.g. sample.executor-provider) that runs controller-spawned dispatch actions when the action omits one. This is not model/runtime provider configuration; pass runtime-specific values in –dispatch-provider-config. Run homeboy agent-task providers for valid ids
--dispatch-model<MODEL>Model override to use for controller-spawned dispatch actions when the action omits one
--dispatch-provider-config<JSON>Agent/model provider config (JSON, @file, or -): the nested AI runtime/provider/model the selected executor uses for controller-spawned dispatch actions when the action omits one. Put runtime-specific provider selection here, not in –dispatch-selector

homeboy agent-task controller mark-human-ready

sh
homeboy agent-task controller mark-human-ready [OPTIONS] <LOOP_ID>

Mark a tracked entity as human-ready work

ArgumentRequiredDescription
<LOOP_ID>yesDurable loop id returned by agent-task controller init
OptionValueDescription
--entity-id<ID>Entity id to mark human-ready
--reason<TEXT>Operator-visible reason stored in loop history

homeboy agent-task controller proof

sh
homeboy agent-task controller proof [OPTIONS]

Run a one-command end-to-end controller proof from a named profile + runner

OptionValueDescription
--profile<NAME>Named proof profile (intent + policy). Resolved from the registry passed via –profiles; the orchestration never branches on the profile name
--runner<RUNNER>Runner to dispatch the proof through (for example a Lab runner id)
--profiles<JSON>Proof profile registry JSON, @file, or – for stdin: a generic object mapping profile names to profile definitions. Keeps profile data out of core so adding a profile is pure data
--seed<SEED>Optional explicit seed material for run-scoped identity. Defaults to a fresh timestamp so each invocation derives an isolated run/loop id
--max-actions<N>Maximum controller actions to execute once preflight passes
--preflight-onlyflagRun preflight reconciliation only; do not dispatch even when it passes