A control surface for OpenCode and local agent runs
Junction supports OpenCode alongside Claude Code and Codex so developers can supervise mixed agent workflows from one browser interface.
Best for
Developers using OpenCode as part of a local agent toolchain.
Why Junction
Junction focuses on orchestration, visibility, and remote control across agent CLIs instead of locking work to a single provider.
What it means
Junction is the local-first control plane for AI coding agents.
One control plane for mixed agent stacks
Developers rarely standardize on one agent forever. Junction is built around the local daemon and run state, so OpenCode can live next to other CLI agents in the same workspace.
Keep supervision consistent
The details of each provider differ, but the operational loop is the same: watch the run, respond when blocked, inspect the branch, and decide whether to continue.
Stay local while adding remote access
OpenCode keeps using the machine where your repo already works. Junction adds the remote browser surface needed to supervise it from another device.
Field notes
Related Junction guides
What OpenCode Users Need From a Control Surface
OpenCode can run in the browser and attach to a terminal, but serious workflows still need remote approvals, notifications, and a broader dashboard.
What an AI Coding Agent Dashboard Should Actually Do
A practical checklist for dashboards that supervise local AI agents well: live streams, approvals, diffs, notifications, and Git state.
How to Manage Multiple AI Coding Agents Across Machines
Learn the workflow for routing AI agent work across a laptop, workstation, and VPS without losing track of approvals, diffs, or status.
Get started
Keep agent work visible from anywhere.
Install the daemon where your projects already run, connect Junction, and use one browser workspace for active AI coding agents.