Operate a run

A Line run records the stages and decisions for one execution. Start with its status and event timeline:

islo factory line-run status <run-id>
islo factory line-run events <run-id>

Use islo factory line runs <line-name> to find run IDs for one Line. islo factory line-run list shows recent runs across Lines.

Send direction

islo factory line-run ask <run-id> --message "Focus on the failing test"
islo factory line-run agent-turn <run-id> --stage-name review --message "Check the updated diff"

ask addresses the Line Manager. agent-turn sends another turn to a successful Agent stage. See Manager and Delegator for roles and Delegations for Slack, GitHub, and Linear.

Stop, retry, or steer

islo factory line-run stop <run-id> --reason "Needs a new scope"
islo factory line-run steer <run-id> review --param input="Review the updated diff" --reason "Scope changed"
islo factory line-run retry <run-id>

stop interrupts current work and parks the Line. It does not cancel the run. Steer a parked or completed run to a stage; steering an active run returns 409, so stop it first. retry reruns the latest failed stage. There is no follow-up or cancel CLI command.

A Line can cap active time, rated spend, and iterations with [limits]. Parked time does not count toward the active-time cap. When a cap is reached, inspect the status and decide whether to steer. A steer can start a new usage window or reset the iteration counter:

islo factory line-run steer <run-id> review --reset-usage --reason "Continue after review"
islo factory line-run steer <run-id> review --reset-iterations --reason "Allow another pass"

--reset-usage opens a fresh active-time and budget window while lifetime billing totals remain. A normal steer or retry keeps the existing window. For stage failures, inspect the factory troubleshooting guide.