Evidence record / opencode

A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.

2026-10-24-opencode-mcp-human-input-forms-reach-clients-and-client-hosted-mcp-arrives-experimentally

MCP human-input forms reach clients, and client-hosted MCP arrives experimentally. 2.1.4 repairs MCP elicitation forms that never appeared: the server-side client now retains the Effect context for SDK callbacks, so form events retain their Location rather than disappearing from the receiving clients. A corresponding UI change renders the forms in desktop and web. The same release adds connectClientMcp and a client MCP WebSocket endpoint, explicitly experimental. This can attach client-hosted tools to a remote server session, but it does not make every client-hosted integration stable or remove server/client compatibility requirements. Tagged MCP docs still default to the legacy protocol and document explicit configuration for the newer 2026-07-28 protocol.

Channel: tagged-release. Half: both. Date: 2026-10-23.

Operator consequence: Upgrade the server and affected desktop/web client together before retesting a stalled human-input MCP workflow. Exercise a real form round trip and rejection, not just tool discovery. For client-hosted MCP, pin the 2.1.4 client library and keep the pilot bounded until disconnect, reconnection and authorization behavior are verified. The attention benefit is making an actual human decision visible; a faster tool loop is irrelevant when the required approval never reaches the person.

Receipt

Finding metadata

Run: 2026-10-24-weekly-digest-2026-10-13_2026-10-24-frontier-v0

Finding ID: 2026-10-24-opencode-mcp-human-input-forms-reach-clients-and-client-hosted-mcp-arrives-experimentally

Profile citations

Source links

Primary links, including exact changelog lines when available.

Versioned source: run artifact