- In OpenCode 2.0, the terminal, web, and desktop apps all connect to a single background server process, according to the original. Previously, this server approach was mainly used by advanced users who started it themselves.
- The original explains that an agent can hand long tasks to sub-agents or background shell commands, and tasks already running can be moved to the background with a shortcut key. This lets users keep giving the next instruction without stopping the main task.
- The original says that code mode, which turns MCP servers or OpenAPI endpoints into functions the agent can call from within a script, is applied by default to the MCP server in 2.0. The claim that multiple tool calls can be combined into one round trip is the development team's explanation, and the original contains no independent verification of it.
- About the plugin system, the original says 2.0 implements 80 or more features as internal plugins. This is what the development team stated, and it is not a figure confirmed externally.
O: Developers who run several tasks in parallel with a development agent may want to test a flow where test runs are handled by a background shell while they keep making other changes.
X: According to the original text, the 1.0 plugin does not work on 2.0, and the server API has changed completely, so existing scripts need migration. The performance claims are the development team's own explanation.