Upstream: mcpc pollTask() returns statusMessage instead of actual result

[jirispilka]

Problem

The mcpc pollTask() detached polling fallback (mcp-cli/src/core/mcp-client.ts, ~line 715) returns the statusMessage as fake content instead of fetching the actual stored result via tasks/result:

// Current behavior (incomplete):
if (task.status === 'completed') {
    return { content: [{ type: 'text', text: task.statusMessage || 'Task completed' }] };
}

// Fix:
if (task.status === 'completed') {
    const result = await this.getTaskResult(taskId);
    return result;
}

This means detached tasks polled via pollTask() lose their actual result — the client only sees the statusMessage text.

Scope clarification: this only affects the detached polling path (callToolDetached + manual pollTask). The normal callTool path is not affected:

mcpc callTool → callToolStream → requestStream → completed → getTaskResult ✅
mcpc pollTask → tasks/get loop → completed → statusMessage as content ❌ (detached only)

References

• res/task_status_workaround.md — full analysis
• fix: Set final statusMessage before storeTaskResult (#638) #680 — PR that introduced the workaround
• Upstream: SDK requestStream() discards results for 'failed' tasks #685 — companion SDK issue

[jancurn]

I'll look into this, created an issue

[jirispilka]

The issue was marked as invalid in the mcp-cli, Closing it here