opencode

Use `opencode run 'your prompt'` in the target repository workdir for bounded, non-interactive tasks. Attach context files with `-f`, force a model with `--model provider/model`, and show reasoning with `--thinking`.

Run `opencode pr 42` in the repository to use the built-in PR command. For isolation, clone the repo into a temporary directory and run a review prompt with the changed files attached via `-f`.

Yes, interactive TUI sessions require `pty=true` when launched in the background. The `opencode run` one-shot command does not need a pty and works as a plain terminal command.

PATH mismatches can resolve different OpenCode binaries or model configs. Check with `which -a opencode` and `opencode --version`, and pin an explicit binary path such as `$HOME/.opencode/bin/opencode` if needed.

Send Ctrl+C (`\x03`) via the process write action or kill the process directly. Do not use `/exit`, which is not a valid OpenCode command and opens an agent selector dialog instead.

Yes, launch separate background sessions scoped to distinct workdirs or Git worktrees to avoid collisions. Track all sessions with the process list action and monitor each with poll or log.