> NEW TASK
> TASKS
⋯
> LANES
DISCOVERING...
> SETTINGS
Configure fleet dispatch autonomy governance and automated execution gating.
LimitsHow long one agent run may take
How long one agent run (daemon executor or fleet run) may take; then its whole process tree is stopped and the work so far stays on the task's branch. With the grid backend the runner has its own timeout.
Quality gatesWhat has to pass before a task is done
ALWAYS ON
Before a task counts as done: the change stays inside its allowed paths, Python still parses, the repository gate passes (projects.<name>.gate, verify.sh or pytest), the task's own test passes and the files it claimed changed. The gates run in the agent's sandbox without credentials. They cannot be switched off here: a task that skipped them would not be verified.
Keys and sandboxWhere provider keys come from; the kernel sandbox
LANDLOCK + SECCOMP SANDBOX
Agent CLIs write only to their worktree and their own state. Not switchable from the web: only FLEET_SANDBOX=0 in the daemon's environment turns it off.
checking...
COORDINATOR
…

Who coordinates the fleet: writes the task specs, reviews the results, answers approvals. Recorded with every task and shown in both dashboards. It does not change which lane runs a task; the router does that.

ROUTING STRATEGY: Router: measured pass rate per category over cost, failover with one repair pass
SANDBOX ISOLATION: checking...
CODE INTEGRITY: Scope, syntax, repository gate, task gate