[BUG]: opencode doesn't receive progress notifications from MCP servers #24965

Description

Description

opencode's MCP client never processes notifications/progress from any
MCP server. Long-running tool calls that rely on progress notifications
to keep the SDK's per-request timer alive (via resetTimeoutOnProgress)
fail with:

MCP error -32001: Request timed out

even when the server is healthy and emitting progress on schedule.

Root Cause

The MCP TypeScript SDK only injects a progressToken into outbound
_meta when options.onprogress is set
(https://github.com/modelcontextprotocol/typescript-sdk/blob/v1.27.1/src/shared/protocol.ts#L1126-L1135).
opencode's client.callTool passes resetTimeoutOnProgress: true but
does not pass onprogress, so:

• No progressToken is sent to the server, so the server has no token
  to address its progress notifications to.
• Even if the server emitted a notification with a fabricated token,
  the SDK's _onprogress would early-return on "unknown token" before
  reaching the timer-reset block.

The result is that resetTimeoutOnProgress: true is dead code for any
opencode tool call: the per-request timer fires unconditionally at the
SDK default of 60s, regardless of how often the server emits progress.

Steps to Reproduce

1. Configure any MCP server that emits notifications/progress during
   a tool call (e.g. a test server that sleeps and emits progress every
   20s).
2. Invoke the tool from opencode.
3. Observe that the call times out at -32001 even though the server
   completes the call successfully.

Expected Behavior

opencode should receive and process notifications/progress. With
resetTimeoutOnProgress: true, each notification should reset the
per-request timer, allowing long-running tools to complete.

Plugins

No response

OpenCode version

No response

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response