💡 MCP Tasks Integration: Avatar-Narrated Long-Running Operation Tracking via 2026-07-28 Spec

[github-actions[bot]]

Summary

Integrate the new MCP Tasks extension (formalized in the 2026-07-28 specification, released July 28, 2026) to enable reliable tracking, progress reporting, and graceful cancellation of long-running MCP tool operations. The avatar narrates progress conversationally ("Your report is 60% done — data analysis is complete, now writing the executive summary"), handles task failures with recovery options, and supports the new poll-based tasks/get mechanism with subscriptions/listen for change notifications. This extends TalkTerm's existing progress display (FR43) beyond Claude Agent SDK message streams to cover the entire MCP tool ecosystem.

Market Signal

The MCP 2026-07-28 specification (released 3 days ago) formally moved Tasks from experimental to the stable io.modelcontextprotocol/tasks extension. MCP surpassed 400M monthly SDK downloads with 4x growth in 2026, cementing its position as the industry standard for connecting AI agents to applications. The stateless protocol redesign means MCP servers can now run on serverless/edge infrastructure behind standard load balancers. Tasks was the #1 requested capability for production agent systems — a partner noted it enables tools to "confirm with the user before it acts, like the cost of a new project before it's created, or a query that would delete data." Early adopters of the new spec gain first-mover advantage in the rapidly growing MCP ecosystem.

User Signal

Existing idea #366 (MCP 2.0 Protocol Readiness) covers native Apps rendering and long-running tasks at a high level. This proposal focuses specifically on the Tasks extension's integration with TalkTerm's avatar-narrated UX — making long-running operations feel natural through conversational progress updates rather than silent progress bars. FR43 (live task progress display) provides the UI foundation but currently only tracks Claude Agent SDK message streams, not MCP Tasks events. Non-technical users especially need conversational progress: a progress bar at 60% tells them nothing, but "data analysis is complete, now writing the summary" tells them everything.

Technical Opportunity

The MCP Tasks extension defines a standard poll-based tasks/get mechanism with subscriptions/listen for change notifications — TalkTerm's IPC streaming pattern (contextBridge + ipcMain/ipcRenderer) already handles real-time message passing between processes. The AgentBackend abstraction layer can integrate Tasks progress events alongside SDK message streams through a unified TaskProgressAdapter interface. The Tasks extension's confirm-before-act pattern aligns directly with TalkTerm's FR20 confirmation gate. The stateless MCP core means TalkTerm can connect to Tasks-enabled MCP servers without maintaining persistent connections — crucial for reliability on desktop where network conditions vary.

Assessment

Dimension	Score	Rationale
Feasibility	high	MCP TypeScript SDK is already updated for 2026-07-28 spec. Tasks extension uses standard poll + subscribe patterns that map cleanly to TalkTerm's existing IPC streaming architecture
Impact	med	Improves UX for long-running operations (report generation, data import, CI triggers). Impact grows as the MCP tool ecosystem expands and more servers adopt Tasks
Urgency	high	Spec released July 28, 2026 — 3 days ago. Early adoption establishes TalkTerm as a first-class MCP Tasks host. Designing the TaskProgressAdapter interface now avoids architectural retrofit later

Adversarial Review

Strongest objection: The MCP 2026-07-28 spec is only 3 days old. Implementation may be unstable, third-party MCP servers may not adopt Tasks quickly, and the extension API could still change.

Rebuttal: Tasks moved from experimental to stable in this release — it's been in development for months with partner testing (the partner quote about cost confirmation comes from production use). The TypeScript SDK is already updated. Early adoption risk is manageable: TalkTerm can gracefully fall back to simple status polling when Tasks metadata isn't available from a given MCP server. The avatar narration differentiates TalkTerm regardless of Tasks adoption rate — even basic pending/running/completed/failed status updates are more engaging when spoken by a character than shown as a progress bar.

Suggested Next Step

Update the MCP integration layer design in architecture.md to include Tasks extension support alongside the existing Apps extension reference. Define a TaskProgressAdapter interface in src/shared/types/ports/ that normalizes both SDK message streams and MCP Tasks events into a unified progress model consumable by the renderer's TaskProgress display mode. Implement tasks/get polling and subscriptions/listen in the MCP client wrapper using the updated TypeScript SDK.