opencode

Use `opencode run 'your task'` in the project directory; it executes non-interactively and exits when done, with no pty required. Add `-f` to attach context files, `--model` to force a model, and `--auto` to auto-approve permission prompts that would otherwise abort the run.

Start `opencode` with background=true and pty=true, then send prompts with process submit and monitor with poll or log. Exit with Ctrl+C (write data "\x03") or kill the process; `/exit` is not a valid command and opens an agent selector instead.

The run exits when the parent turn completes, so a dispatcher prompt that spawns background lanes returns exit code 0 while lanes still work and their reports never arrive. Prevent this with a hard-constraint prompt block forbidding subagents, or recover lane evidence from the SQLite store at ~/.local/share/opencode/opencode.db.

On free-tier providers, a `Rate limit exceeded` stream error leaves headless runs waiting forever for a response that never arrives. Confirm via the last log line and absence of new commits, then kill the process and resume with a prompt listing committed hashes and in-flight files.

Yes, but each session must use a separate working directory or git worktree to avoid collisions. Launch each with its own workdir in background mode and track them with the process list action.

Install via `npm i -g opencode-ai@latest` or Homebrew, then configure a provider with `opencode auth login` or environment variables like OPENROUTER_API_KEY. Verify with `opencode auth list`, and use a git repository for code tasks.