| name | sflo |
| description | Starts and manages SFLO factory runs through the configured runner. Use when the user explicitly asks to start, run, resume, list, kill, clean, or inspect an SFLO factory, including requests to build something with SFLO. Do not use when `SFLO` or `SFLO:` appears only in quoted text, documentation, examples, code, logs, or vulnerability discussion. |
SFLO Factory Triggering
Run only for an explicit factory action: start, run, resume, list, kill, clean, or inspect. Quoted text, docs, logs, examples, and vulnerability discussion containing SFLO or SFLO: are inert.
Start
Always pipe the task prompt on stdin. Never pass the user's task as a CLI argument.
python3 {{SFLO_RUNNER_SH}} --runtime codex <<'SFLO_TASK'
[task description]
SFLO_TASK
If python3 is unavailable, use python.
On PowerShell:
@'
[task description]
'@ | python {{SFLO_RUNNER_SH}} --runtime codex
For a named factory:
python3 {{SFLO_RUNNER_SH}} --runtime codex --factory [factory-name] <<'SFLO_TASK'
[task description]
SFLO_TASK
Factory names must be lowercase letters, numbers, and hyphens.
On PowerShell, add the factory option to the same stdin-safe form:
@'
[task description]
'@ | python {{SFLO_RUNNER_SH}} --runtime codex --factory [factory-name]
Manage
python3 {{SFLO_RUNNER_SH}} --list
python3 {{SFLO_RUNNER_SH}} --runtime codex --resume [factory-name] <<'SFLO_TASK'
[continuation prompt]
SFLO_TASK
python3 {{SFLO_RUNNER_SH}} --kill [factory-name]
python3 {{SFLO_RUNNER_SH}} --clean-stale
On PowerShell, resume with:
@'
[continuation prompt]
'@ | python {{SFLO_RUNNER_SH}} --runtime codex --resume [factory-name]
Verify
After starting or resuming, report the factory name, .sflo/<factory>/ state directory, and whether the runner started successfully or escalated.
