Run OpenCode in parallel.
A worktree and terminal per task, a private OpenCode server in each, status from its session events, and the ouijit command in its context. Nothing to configure.
A worktree and terminal per task, a private OpenCode server in each, status from its session events, and the ouijit command in its context. Nothing to configure.
Knows OuijitAn Ouijit plugin adds the ouijit CLI reference to each session, so OpenCode can create tasks, move cards and stage review comments without being told how.
Live statusThe same plugin listens to OpenCode's session events and reports when a turn starts and ends. The card shows thinking or ready.
A server per terminalOpenCode 2 normally shares one background server across every terminal. In Ouijit each terminal gets its own, so a session runs in that terminal's sandbox and ends when the terminal closes.
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
opencode
# Continue · a task already in progress is reopened; resumes this worktree's newest session
opencode -cYes. The sandbox lets it reach its config directory and the OS keychain. Everything else outside the worktree stays out of reach.
OpenCode 1 and 2. Status and the CLI reference work on both; the private server per terminal applies to OpenCode 2.
No. The opencode on PATH in an Ouijit terminal is a wrapper around the real one, and only there. Utility subcommands such as auth and models pass straight through.