| name | doompi-use-runner |
| description | Use Doom Pi Runner to supervise shell commands, inspect durable logs, provide interactive input, and stop background runs. |
Use Doom Pi Runner
Use Runner for shell work that may outlive one tool call, needs durable logs, or requires later inspection and control.
Launch work
- Use the Runner-provided
bash tool for shell commands.
- Let short commands return inline.
- Set
background: true when the command should detach immediately.
- Set
interactive: true only when the process genuinely needs terminal input.
- Give long foreground work a realistic timeout. Commands that cross the promotion threshold can continue as supervised runners.
Inspect and control work
Use /runners or SPC r l in the TUI. For direct control, use:
doom-runner list
doom-runner status <runner-id>
doom-runner logs <runner-id>
doom-runner input <runner-id> --text "y" --enter
doom-runner stop <runner-id>
doom-runner stop-all
Input requires a running interactive process backed by RMUX. Preserve the returned runner identifier because it remains usable after transcript compaction.
Close the lifecycle
- Inspect logs instead of relaunching a command whose status is uncertain.
- Stop watchers, servers, and failed interactive processes when they are no longer needed.
- Treat commands as running with the Doom Pi process environment and the operating-system user's privileges.
- Treat logs as sensitive because they may contain prompts, source, output, or credentials.
