OpenCode adds remote sandboxes and syncs agent state across devices

• OpenCode is moving beyond a local-only coding agent: the team says agents can now run on a laptop, remote server, or cloud sandbox, while state syncs back when the device reconnects distributed OpenCode.
• That shift makes longer-running sessions more practical off-device, and OpenCode's own product page plus a Hacker News discussion thread highlights point to remote access patterns such as opencode serve, multi-backend WebUI setups, and local-model support.
• The product surface is also being pushed into plugins: OpenCode cofounder thdxr says new features will be built as "internal plugins" so the plugin API "will have to be good" plugin pass, with runtime activation also described in internal plugins.
• Desktop workflow changes are landing alongside that architecture work: the next desktop release adds Git and branch visibility in the review panel, shown in OpenCode's review panel demo.

The new capability is distributed execution. In thdxr's description, agents can run "on your laptop, on a remote server, in a cloud sandbox provider," and if you "shut your laptop" the work keeps running; when you reopen it, "all the data syncs" back distributed OpenCode. A follow-up post extends that model to multiple controller devices, including a phone as a remote controller or a cloud-hosted "home server" coordinating other clients device configs.

That matters because OpenCode already spans terminal, IDE, and desktop usage, with support for LSP, multi-session work, shareable session links, and 75-plus model providers including local models, according to the product page. In the Hacker News thread, practitioners also describe opencode serve as reachable "from anywhere," working well with Tailscale, and letting the WebUI connect to multiple backends at once through the remote-workflow comment.

OpenCode is also refactoring around plugins instead of treating them as an edge feature. Thdxr says the team now has "most features" in place and is doing a pass to decompose them into plugins because, since the team "didn't have to use the plugin api," it "never become very good"; from here, "all new features" are expected to ship as internal plugins plugin pass. An OpenCode repost adds the operational detail that features in OpenCode itself can be activated or deactivated at runtime, the same way as external plugins internal plugins.

That design already has real user signals behind it. In the Hacker News thread, one developer says OpenCode is their primary harness for llama.cpp, Claude, and Gemini, and that they built a self-modifying hook system over IPC via a plugin in the extensibility comment. Another says a plugin that prunes and retrieves conversation history feels like an "infinite context window" in the memory plugin comment.

The product story is stronger than the operational story right now. The public demo language around remote sandboxes stresses that the current UX is "temporary" and only demonstrates the primitives distributed OpenCode, so deployment details still look in flux.

Operators also have a few concrete checks to make. The Hacker News discussion surfaces praise for deployment flexibility, including homelabs, containers, and bubblewrap sandboxing, but it also raises a telemetry concern: one commenter says OpenCode sends telemetry to its own servers "even with local models," with "no option to disable it," as summarized in thread highlights. Separately, the next desktop release is broadening the review surface with visible Git and branch changes in the review panel, shown in review panel demo and the attached review panel video.