Guides
Choose a conduction mode
Compare the HITL points and the limits of each mode.
Choose by the decision required
#Classic has three HITL points: goal, plan and evidence. #Maestro concentrates its HITL point on assumptions and the plan. #Auto runs the full cycle without a scheduled HITL point. Blocking conditions and escalations remain active in all three.
ork modos
ork modos --do-pedido "revisar a documentação #Maestro"The limits of #Fast
#Fast runs only GO, with evidence proportionate to a small request. It does not grant automatic push permission or allow changes to protected public contracts. Changes to the mode matrix, schemas or integration contracts require a full-cycle mode.
Check the manifest
Without a tag, conduction.default_mode applies. The core checks the choice against conduction.allowed_modes. A tag does not authorize ignoring the owner’s explicit scope.
Profile rotation on quota
With quota rotation on, the default, an exhausted quota, credit or plan limit marks the profile and moves to the next active profile of the same runtime. The prompt that follows depends on what the session produced: with no output, the original prompt goes; with output, a resume prompt with the checkpoint goes. Without an active profile, the core moves to the block’s fallback runtime and then to the durable queue. An ordinary short-window rate limit never rotates profiles: it waits for the window in the queue.
The checkpoint carries the phase, HEAD, worktree state, claims and round, preserves the original prompt and SHA-256 and says to continue without repeating GOAL or PLAN. Partial output does not receive the original prompt over the changed worktree; without a safe resume, the session becomes human.pending. In #Classic the block waits for the answer to ork gate request; in #Maestro and #Auto it rotates on its own and records runtime_profile_rotated with who decided, the evidence and the reason. Exceeding retry.max_tentativas stops any mode, including #Auto, and a profile is not an axis of CHECK independence.
ork accounts
ork setup <mode>Codex only
The default setup dispatches blocks through claude-bg. To use only Codex, move every block of the allowed modes to it; ork setup <mode> lists the blocks. ork doctor fails on a missing claude binary only while a block of an allowed mode still dispatches through claude-bg; a fallback that lands on it only produces a warning.
ork setup classic
ork setup classic --bloco 1 --runtime codex --model <modelo>The thread worktree
The mode decides how many HITL points a thread has; the worktree decides where it writes. With worktree.por_thread: true, the value written by ork init, ork thread new creates the worktree and the ork/<slug> branch in any mode, without a flag, and ork ship delivers that branch. With the key set to false or missing, the worktree is only created with --worktree auto or by a cycle that requires it.
--worktree <DIR> reuses an existing directory. --sem-worktree creates the thread at the project root: on the base branch, ork ship is blocked by push_direto_na_base: block, the ork init default, and before GO ork worktree ensure <thread> can still create the worktree. --dry-run shows the worktree and branch that would be created, or why creation would be refused. The greenfield, merge-branch and feature-xl-faseada cycles require a worktree and refuse --sem-worktree. In a repository without commits, the thread starts at the root with a warning.
ork thread new "corrigir o filtro" --modo classic --dry-run
ork thread new "corrigir o filtro" --modo classic --sem-worktree
ork worktree ensure <thread>