Run Pi in parallel.
A worktree and terminal per task, status from a Pi extension Ouijit installs, and the ouijit command in its system prompt. Nothing to configure.
A worktree and terminal per task, status from a Pi extension Ouijit installs, and the ouijit command in its system prompt. Nothing to configure.
Knows OuijitThe ouijit CLI reference is appended to the system prompt at launch, so Pi can create tasks, move cards and stage review comments without being told how.
Live statusPi exposes its lifecycle to extensions, so Ouijit installs a small one and loads it at launch. It reports when a turn starts and ends, and the card shows thinking or ready.
SandboxedRun it with its permission prompts off inside Ouijit's sandbox and the kernel holds it to the task's worktree. The dev server beside it stays on the host.
What the project runs when a task changes status. Set them in project settings, or ask the agent to.
# Start · a task moves to In Progress
piYes. The sandbox lets it reach its config directory and the OS keychain. Everything else outside the worktree stays out of reach.
No. The pi on PATH in an Ouijit terminal is a wrapper around the real one, and only there. Pi's own subcommands, such as install and config, pass straight through.