OpenCode v1.17.4 Released but Renderer Local Server Connection Fails
coding-agents opencode developer-tools mcp solidjs
trending_up Trend: coding-agents

OpenCode v1.17.4 Released but Renderer Local Server Connection Fails

calendar_month June 12, 2026

OpenCode v1.17.4 Released but Renderer Local Server Connection Fails

Summary

On June 12, 2026, OpenCode released version v1.17.4, introducing helpful features like workspace-relative cwd support for local MCP servers. However, a critical bug in the desktop application is preventing users from connecting. A runtime error in the SolidJS state management of the renderer causes the app to lose the session credentials, resulting in a persistent “Could not reach Local Server” loop.

What happened?

  • Release of v1.17.4: OpenCode released v1.17.4 on June 12, adding features like cwd support for local MCP servers and connector-based auth flows.
  • Renderer Runtime Error: Desktop app users report a crash with the stack trace props.api.state.session.get is not a function from the opencode-visual-cache package.
  • Connection Failure: The UI receives the password during the handshake but fails to store it in the SolidJS state, causing the local server connection to fail.
  • Affected Users: All developers running the OpenCode Desktop application who updated to the new v1.17.4 release.

Why it matters

Local MCP (Model Context Protocol) servers are key to integrating AI coding agents with local filesystems and development tools. When the renderer fails to connect to the local server, the agent’s main features become completely inaccessible. This highlights the vulnerability of frontend state-management libraries during minor version upgrades, calling for developer caution before performing app updates.

Evidence

  • Changelog: The official OpenCode Changelog details the release of v1.17.4 and its focus on local MCP server improvements.
  • GitHub Issue: Bug report #32045 documents the exact error props.api.state.session.get is not a function in opencode-visual-cache/src/index.tsx at line 442.
  • User Reports: Multiple users have confirmed the issue on GitHub, stating that the desktop app is stuck on a blank connection screen.

Analysis

The root cause lies in how the newly updated opencode-visual-cache package interacts with the SolidJS state store of the Desktop app. During the connection initialization, the renderer attempts to fetch the session ID using props.api.state.session.get(sid). However, due to state loss or an incorrect object prototype binding, the get method is undefined on the session object. This results in an unhandled exception that stops the execution flow of the renderer, leaving the app in a broken state.

Practical Takeaways

  • Decline the Update: Desktop users should hold off on updating to v1.17.4 until a hotfix (likely v1.17.5) is released.
  • CLI Workaround: The command-line interface (CLI) version of OpenCode remains fully functional and is unaffected by this renderer bug.
  • Rollback to v1.17.3: If you have already updated and are locked out, downgrade to version v1.17.3 to restore connection stability.

Open Questions

  • When will the core maintainers release a hotfix to address this SolidJS state regression?
  • How did this critical runtime error slip through pre-release testing and CI checks?

Sources

  1. OpenCode Changelog
  2. OpenCode GitHub Releases
  3. GitHub Issue #32045: props.api.state.session.get is not a function