Operating workflows from the CLI
Operators use lmctl to inspect state, start workflows, answer escalations, and
track issues through lmctl commands.
Orient first
Start each operating session with:
lmctl status
lmctl api attentions --json
lmctl status is context-aware. When you run it inside a project
directory, it reports that project. Outside a project, it still reports profile,
provider, run, and attention information.
Common requests
| Operator goal | Command |
|---|---|
| See what is happening | lmctl status |
| See open attentions | lmctl api attentions --json |
| Run QA for a project | lmctl api submit-job --workflow qa-suite --inputs '{"project_name":"my-project"}' --project my-project |
| List open issues | lmctl api issues list my-project --status open --json |
| Read one run | lmctl api run <id> |
| List recent runs | lmctl api runs |
Reuse a team as a template
Use clone when you want to copy a .lmctl teamfile without carrying over the
source team's session ids:
lmctl clone ./backend/backend.lmctl ./backend-v2/backend-v2.lmctl
lmctl lint ./backend-v2/backend-v2.lmctl
lmctl seed ./backend-v2/backend-v2.lmctl
When one team needs to reach a member in another team, no setup is required: cross-team calls work automatically at runtime, with runtime cycle protection against runaway loops. See Cross-team calls for the semantics.
Answer workflow escalations
Some workflows pause for human input. List pending escalations:
lmctl api escalations list --json
Respond to one escalation by id:
lmctl api escalations respond <attention_id> "Use the smaller scope and continue."
The integrated escalation command handles the workflow response and attention acknowledgement together.
File project issues
Use issues for bugs, failed QA chapters, and follow-up work:
lmctl api issues create my-project \
--title "Status endpoint returned 500" \
--body "Expected status data, received HTTP 500 during the smoke test." \
--severity high \
--labels '["api","smoke"]' \
--ai-test-path "ai-test/api-status-ok.md"
Close an issue after the fix is verified:
lmctl api issues close <id> --commit-hash <sha>