Submit an agent task, run its gates, and open a pull request
homeboy agent-task cook-continue
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
homeboy agent-task loop
no help text
homeboy agent-task run-plan
no help text
homeboy agent-task run
no help text
homeboy agent-task run-next
no help text
homeboy agent-task submit
no help text
homeboy agent-task status
no help text
homeboy agent-task list
no help text
homeboy agent-task active
no help text
homeboy agent-task reconcile
Preview or apply reconciliation for one durable run
homeboy agent-task reconcile-records
no help text
homeboy agent-task latest
no help text
homeboy agent-task logs
no help text
homeboy agent-task artifacts
no help text
homeboy agent-task retained-artifacts
Discover or attach selected outputs retained in a terminal Lab Cook workspace
homeboy agent-task evidence
no help text
homeboy agent-task diagnose
no help text
homeboy agent-task runtime-recover
Recover a missing or corrupted immutable controller runtime pin
homeboy agent-task runtime-validate
Validate controller runtime eligibility without executing provider work
homeboy agent-task replay-provider-boundary
no help text
homeboy agent-task cancel
no help text
homeboy agent-task resume
no help text
homeboy agent-task retry
no help text
homeboy agent-task fanout
no help text
homeboy agent-task review
no help text
homeboy agent-task promote
no help text
homeboy agent-task adopt
Adopt an immutable commit candidate through a tracked cook’s normal gates and finalization
homeboy agent-task finalize-pr
no help text
homeboy agent-task accept
Record an independent, durable acceptance verdict for a candidate
homeboy agent-task gate-feedback
no help text
homeboy agent-task providers
no help text
homeboy agent-task prompts
no help text
homeboy agent-task contract
no help text
homeboy agent-task compile-loop
no help text
homeboy agent-task auth
no help text
homeboy agent-task controller
no 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.
Option
Value
Description
--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
--repair
flag
no 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.
Option
Value
Description
--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-only
flag
Persist 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-gates
flag
Re-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-finalize
flag
Stop 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
--full
flag
Return 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-acceptance
flag
Require a separate durable acceptance verdict before PR finalization
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
Argument
Required
Description
<COOK_OR_ATTEMPT_ID>
yes
Durable Cook ID or one of its provider attempt IDs
Option
Value
Description
--full
flag
Include 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.
Subcommand
Summary
homeboy agent-task loop define
no help text
homeboy agent-task loop status
no help text
homeboy agent-task loop resume
no help text
homeboy agent-task loop stop
no 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.
Argument
Required
Description
<SPEC>
yes
no help text
Option
Value
Description
--on
flag
no help text
--off
flag
no help text
--revolution-limit
<N>
no help text
--resume
flag
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 status
sh
homeboy agent-task loop status <LOOP_ID>
This command declares no clap help text, so no description can be generated for it.
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).
Argument
Required
Description
<ISSUE_URL>...
yes
no help text
Option
Value
Description
--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-gates
flag
Re-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-run
flag
no help text
--run-plan
flag
no 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.
Option
Value
Description
--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.
Option
Value
Description
--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.
Option
Value
Description
--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.
Argument
Required
Description
<BATCH_ID>
yes
no 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
Argument
Required
Description
<BATCH_ID>
yes
no 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.
Argument
Required
Description
<BATCH_ID>
yes
no 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.
Option
Value
Description
--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.
Argument
Required
Description
<RUN_ID>
yes
no help text
Option
Value
Description
--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.
Argument
Required
Description
<SOURCE>
yes
no help text
Option
Value
Description
--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-run
flag
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-gates
flag
Re-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.
Adopt an immutable commit candidate through a tracked cook’s normal gates and finalization
Argument
Required
Description
<RUN_OR_COOK_ID>
yes
Existing durable run id or cook id whose recipe owns the candidate lifecycle
Option
Value
Description
--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-interrupted
flag
Replace a stale interrupted adoption while retaining its lifecycle evidence
--full
flag
Return 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.
Option
Value
Description
--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
--preflight
flag
Validate the complete hydrated dossier and candidate without publishing
--manual-finalization
flag
no help text
homeboy agent-task accept
sh
homeboy agent-task accept [OPTIONS] <RUN_ID>
Record an independent, durable acceptance verdict for a candidate
Argument
Required
Description
<RUN_ID>
yes
no help text
Option
Value
Description
--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.
Option
Value
Description
--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.
Option
Value
Description
--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-readiness
flag
no help text
--refresh
flag
no help text
--catalog
flag
Return 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)
--full
flag
Return 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.
Subcommand
Summary
homeboy agent-task prompts save
Save a markdown prompt in Homeboy’s agent-task prompt store
homeboy agent-task prompts list
List stored agent-task prompts
homeboy agent-task prompts show
Show a stored agent-task prompt
homeboy agent-task prompts remove
Remove 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
Argument
Required
Description
<NAME>
yes
Stable prompt name. Unsafe path characters are normalized for storage
Option
Value
Description
--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
Argument
Required
Description
<NAME>
yes
Stored prompt name or id
homeboy agent-task prompts remove
sh
homeboy agent-task prompts remove <NAME>
Remove a stored agent-task prompt
Argument
Required
Description
<NAME>
yes
Stored 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.
Option
Value
Description
--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.
Option
Value
Description
--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.
Subcommand
Summary
homeboy agent-task auth status
Show redacted readiness for provider secret environment variables
homeboy agent-task auth set-keychain
Store a provider secret in the OS keychain and map it to a required env name
homeboy agent-task auth set-config
Store a provider secret in Homeboy global config and map it to a required env name
homeboy agent-task auth set-keychain-bundle
Store a JSON secret bundle in one OS keychain item
homeboy agent-task auth map-env
Map a required provider env name to another process env var
homeboy agent-task auth map-keychain-bundle
Map a required provider env name to a field in a JSON keychain bundle
homeboy agent-task auth remove
Remove 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
Option
Value
Description
--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
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.
Argument
Required
Description
<SPEC>
yes
Repo loop spec JSON, @file, or – for stdin
Option
Value
Description
--resume
flag
Execute 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-stale
flag
On –resume, automatically reset stale persisted controller state and re-create it from this spec
--replace
flag
On –resume, discard stale persisted controller state and re-create it from this spec
--fork
flag
On –resume, apply this spec under a derived fork loop id, leaving the original untouched
--resume-existing
flag
On –resume, accept stale/mismatched persisted state and resume the existing controller as-is
--doctor
flag
Compile 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
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.
Argument
Required
Description
<SPEC>
yes
Repo loop spec JSON, @file, -, or a generator manifest that writes a spec file
Option
Value
Description
--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-stale
flag
One-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
--replace
flag
Discard stale persisted controller state and re-create it from this spec before running
--fork
flag
Apply this spec under a derived fork loop id, leaving the original controller untouched
--resume-existing
flag
Accept 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
Validate a proof, materialized spec, or controller record for deterministic handoff
Argument
Required
Description
<JSON>
yes
Proof 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
Argument
Required
Description
<SPEC>
yes
Controller 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
Argument
Required
Description
<LOOP_ID>
yes
Durable loop id returned by agent-task controller init
Option
Value
Description
--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
Render the controller failure tree for failed child actions
Argument
Required
Description
<LOOP_ID>
yes
Durable loop id returned by agent-task controller init
Option
Value
Description
--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
Claim and execute the next pending controller action
Argument
Required
Description
<LOOP_ID>
yes
Durable loop id returned by agent-task controller init
Option
Value
Description
--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
Argument
Required
Description
<LOOP_ID>
yes
Durable loop id returned by agent-task controller init
Option
Value
Description
--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
Execute pending controller actions until no executable action remains
Argument
Required
Description
<LOOP_ID>
yes
Durable loop id returned by agent-task controller init
Option
Value
Description
--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
Durable loop id returned by agent-task controller init
Option
Value
Description
--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
Option
Value
Description
--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-only
flag
Run preflight reconciliation only; do not dispatch even when it passes