CLI reference

The CLI follows the factory workflow. Authenticate, select a factory, prepare a Machine, create an Agent, deploy a Line, and inspect its run. Use islo schema <command> to see the installed command and manifest schema.

islo login
islo factory list
islo factory set <factory-key> --project
islo factory machine list
islo agent list
islo factory line list
islo factory line-run list

islo factory current shows the project factory. Most factory and Knowledge commands accept --factory <key-or-uuid> when you want a different factory for one command. The default /factory/... API paths and scoped /factories/{factory_id}/... paths are described in the factory model.

Command groups

Group	Use
`islo factory`	Select a factory; deploy Lines; manage Machines, triggers, and runs
`islo agent`	Validate, create, update, and list Agents
`islo schema factory`, `islo schema agent`	Inspect live Line and Agent manifest schemas
Authentication and API keys	Sign in or authenticate scripts
Project setup and islo.yaml	Configure direct sandbox use
Sandbox commands and Agent integration	Work directly in a sandbox
Utilities	Diagnose the CLI and inspect schemas

The factory overview explains the product. Advanced platform covers sandboxes, snapshots, gateways, and sharing used by factory stages.

Run control

islo factory line run <line-name> --param input="Review pull request 123"
islo factory line-run status <run-id>
islo factory line-run events <run-id>
islo factory line-run ask <run-id> --message "Focus on the test failure"
islo factory line-run stop <run-id> --reason "Needs a different scope"
islo factory line-run steer <run-id> <stage> --reason "Resume with updated scope"

stop parks the run. It does not cancel it. See operate a run for retry, Agent turns, and usage resets.