Use OpenCode directly in the terminal, desktop app, or IDE.
Investigating a bug, trying local edits, or comparing its free models on a prompt belongs in a live session, with you steering each step.
ProPR and OpenCode: a shared PR path for an open-source agent
OpenCode works in the terminal, desktop app, IDE, or browser, and is one of the five agents ProPR runs. Use it directly for exploration, and through ProPR when the work needs planning, shared review, and GitHub follow-up.
vs
OpenCode
Direct, or inside ProPR
OpenCode is both a standalone agent and a supported agent inside ProPR. The same MIT-licensed CLI runs a live session on your laptop or an unattended task on your server.
OpenCode pathTerminal, desktop, or IDE session → local edits →
/opencode on GitHubYou steer each step and decide what reaches review.ProPR pathPlan → isolated workspace → GitHub PR → follow-up commitA plain comment drives the follow-up; no Action, no workflow file.
OpenCode is Anomaly's MIT-licensed coding agent. It runs as a terminal UI, a desktop app, a VS Code extension, and a local web UI, against any model provider you authenticate, with free models included and an optional OpenCode Go subscription from $10 per month for a curated model set. It shines at live debugging, tight loops, local experiments, and pairing with a model while you keep direct control of the repository. Its GitHub Action answers /opencode mentions on issues and pull requests, opening a PR for an issue or committing to the PR it was mentioned on.
OpenCode inside ProPR runs the same CLI unattended on your server, on its free models, an OpenCode Go subscription, or the provider you authenticate. ProPR adds what the Action leaves out: a plan approved before code starts, a PR review by a second model, and a task record with logs and cost. Its /opencode mention needs the Action and a workflow file; in ProPR a plain comment on the PR is enough, and the follow-up runs on OpenCode or any of the other four agents.
OpenCode versus ProPR.
| Question | OpenCode | ProPR |
|---|---|---|
| License | MIT | Apache 2.0 |
| Live local coding in a terminal | Yes | No, unattended runs |
| Plan approval before code | No | Yes |
| GitHub comments become commits | Yes: /opencode mentions through its GitHub Action | Any plain comment, any agent |
| Shared task record, logs, and cost | No | Yes |
Run OpenCode through ProPR when the change is a task.
Scope it, let ProPR plan it, and get back a pull request with a scored review and usage per run. OpenCode shares that path with Claude Code, Codex, Antigravity CLI, and Mistral Vibe, so a Claude run can pick up where an OpenCode run stopped.
Verified November 2026: opencode.ai, OpenCode GitHub Action, OpenCode Go, OpenCode repository.
Use OpenCode with ProPR.
Stays in OpenCode
- Terminal, desktop, IDE, and browser sessions for live debugging and local experiments.
- Comparing its free models on a prompt while you keep direct control of the checkout.
- Your OpenCode Go subscription or provider login; ProPR signs in with the same account.
Moves to ProPR
- Scoped tasks that should come back as a pull request, with the plan approved first.
- Follow-up commits from plain GitHub comments, with no
/opencodeAction or workflow file. - A second-model review, task history, logs, and usage per run.
Wire them together
Sign in OpenCode inside ProPR
Install ProPR (quickstart) or pick a ProPR Hosted plan, add the repository, and sign in OpenCode with its free models, OpenCode Go, or the provider you authenticate.
Keep the terminal for thinking, send tasks to ProPR
Investigate in a live session as before. When the change has a shape, write it as a GitHub issue and add the AI label, or run propr issue implement; ProPR plans it, runs OpenCode in isolation, and opens the pull request.
Steer from the pull request
A plain comment becomes the next commit, from OpenCode or any of the other four agents. If the OpenCode GitHub Action also watches the repository, retire its workflow file so one path answers comments. The follow-up playbook walks one comment to its commit.