Run Codex in parallel.
A worktree and terminal per task, status from Codex's own hooks, and the ouijit command in its developer instructions. Nothing to configure.
A worktree and terminal per task, status from Codex's own hooks, and the ouijit command in its developer instructions. Nothing to configure.
Knows OuijitThe ouijit CLI reference is passed to Codex as developer instructions at launch, so it can create tasks, move cards and stage review comments without being told how.
Live statusCodex's own hooks report when a turn starts and ends. Ouijit passes them as config overrides and marks them trusted, so Codex never prompts about them. The card shows thinking or ready.
SandboxedRun it with approvals and its own sandbox bypassed inside Ouijit's sandbox and the kernel holds it to the task's worktree. Codex's sandbox covers the commands it runs; Ouijit's wraps the whole terminal, so anything Codex starts is inside too.
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
codex "$OUIJIT_TASK_DESCRIPTION"The start hook with its permission checks off, for a project that runs inside the sandbox.
codex --dangerously-bypass-approvals-and-sandbox "$OUIJIT_TASK_DESCRIPTION"Yes. The sandbox lets it reach its config directory, the OS keychain and auth.openai.com. Everything else outside the worktree stays out of reach.
No. The codex on PATH in an Ouijit terminal is a wrapper around the real one, and only there.