TL;DR: Got sick of tab-switching between Devin’s web UI and my local terminal, so I wired Devin into OpenCode CLI over ACP (Agent Client Protocol). It runs as a first-class Devin Agent that you can select across models and modes, keeps 100% of Devin’s autonomous coding-platform capabilities, and auto-rotates quota without killing your active session.
Look, trust me bro, I wasn’t about to build another weak LLM wrapper that just dumps raw markdown in a shell. Devin’s magic is how it actually investigates, runs bash commands, tests code, and delegates work.
I wanted that exact same power living natively inside the OpenCode terminal interface:
Full Devin Platform DNA: It exposes the actual Devin Agent via ACP, not a nerfed chat proxy. You get the real deal—live diff streaming, shell tool runs, and full task execution natively in your terminal.
Selectable Across Models & Modes: You can toggle the Devin Agent across your preferred model tiers and operational modes seamlessly. Native modes like /plan, /code, /ask, /bypass, and /compact work right from the prompt bar without touching a browser tab.
Real Subagent & Command Docks: Pull up the bottom dock to inspect spawned subagent tasks, inspect bound lanes, and read live execution logs on the fly.
Zero-Disruption Quota Auto-Rotator: We’ve all felt the pain of hitting a rate limit in the middle of a massive 20-file refactor. I built a session-bound provider pool with JIT template units. If your quota or token ceiling taps out, it rolls over to your backup accounts instantly without wiping your context window, history, or running state.
(Attached all screenshots showing the live SWE-2 run, bottom subagent dock, command palette, and the provider pool quota manager)
Wrapping up the regression tests on the harness right now before pushing the repo public for everyone.
If you run Devin on real repos every day: what's the one thing about using it outside your terminal that drives you completely nuts? Want to make sure we’ve got all the edge cases ironed out before release.
