opencode v1.17.7 fixes plugin routing and MCP workspace support
opencode v1.17.7 ships a set of bugfixes and improvements across its Core, TUI, Desktop, and SDK layers, including correct plugin server routing, PTY environment variable support, and MCP workspace root delivery.
Score breakdown
The release closes several correctness gaps — particularly plugin server misrouting and PTY environment variable propagation — that could cause silent misbehavior in multi-server and terminal-heavy agentic coding workflows.
- 01Plugin client requests now reuse the active server instead of assuming the default local port
- 02ACP shell tool calls show the command and working directory from the start of execution
- 03Plugin-provided shell environment variables now apply to PTY sessions
opencode v1.17.7 addresses a cluster of correctness issues in its Core layer. Plugin client requests previously assumed a default local port; they now reuse the active server, preventing misrouted calls in multi-server setups. ACP shell tool calls have been updated to surface the command and working directory immediately rather than after execution, improving visibility. Plugin-provided shell environment variables are now correctly propagated to PTY sessions, closing a gap where those variables were previously ignored in terminal contexts. On the improvement side, MCP servers can now receive the current workspace as a client root, enabling workspace-aware tooling.
The TUI's MCP debug tooling has been updated to use the SDK's latest protocol version, keeping debug output aligned with current protocol behavior.
The TUI's MCP debug tooling has been updated to use the SDK's latest protocol version, keeping debug output aligned with current protocol behavior. In the Desktop layer, a routing fix ensures that new session routes stay scoped to their own draft server, so prompts and state are directed at the intended workspace rather than leaking across sessions. The SDK received two improvements: clients now refresh model and provider availability automatically when integrations change, and both credential update and remove calls have been extended to accept a `location` parameter.
Key facts
- 01Plugin client requests now reuse the active server instead of assuming the default local port
- 02ACP shell tool calls show the command and working directory from the start of execution
- 03Plugin-provided shell environment variables now apply to PTY sessions
- 04MCP servers can now receive the current workspace as a client root
- 05MCP debug in the TUI now uses the SDK's latest protocol version
- 06Desktop session routes stay scoped to their own draft server to target the correct workspace
- 07SDK clients refresh model and provider availability when integrations change; credential update and remove calls now accept `location`
Topics
Summary and scoring are generated automatically from the original article. We always link back to the publisher and never republish images or paywalled content. Last processed Jun 15, 2026 · 11:57 UTC. How this works →