Post

Exciting to see @OpenCode 2.0 ship! is a rewrite, not a point release. Here are the highlights.

Code Mode: the agent writes one short JavaScript script that chains tool calls, instead of separate round trips. MCP servers and @OpenAPISpec endpoints become callable functions. I want to try it on workflows that hit several MCP servers in a row.

Dwayne Forde

@dwayne.io

Always-on local server: one background process that the TUI, web interface and desktop app all connect to. Scripts can discover it through the client package, and /pair exposes it to other hosts.

15/10/26, 4:53 pm0 reposts0 likes

Dwayne Forde

@dwayne.io

Always-on local server: one background process that the TUI, web interface and desktop app all connect to. Scripts can discover it through the client package, and /pair exposes it to other hosts.

Dwayne Forde

@dwayne.io

Background tasks: subagents and shell commands can run in the background, and ctrl+b moves running foreground work there. Useful for long test runs while you keep working.

orke | BOMTOBE

@bomtobe-orke.bsky.social

For long test runs, handoff is only useful if the session keeps the final exit code, log tail, and running/waiting/done state visible after you switch away. We build Orke at BOMTOBE to keep terminal, browser result, and Git review together.

Dwayne Forde

@dwayne.io

The API was rebuilt from scratch, and the agent can call its own API, for example to create a git worktree and move a session into it. Agents setting up their own workspace is a nice direction.

Dwayne Forde

@dwayne.io

Plugins: 80+ internal plugins implement the 2.0 features, TUI plugins are now stable, and plugins hot-reload mid-session.