{
  "schema_version": "1.1",
  "id": "s8:https://www.youtube.com/watch?v=s4r6nk5WsZw",
  "slug": "mcp-tasks-async-why-aren-t-any-agents-supporting-them-cornelia-davis-tem-1fnlb47",
  "url": "https://feed7.dev/p/mcp-tasks-async-why-aren-t-any-agents-supporting-them-cornelia-davis-tem-1fnlb47",
  "title": "MCP Tasks (async): Why Aren't Any Agents Supporting Them? — Cornelia Davis, Temporal",
  "why_included": "MCP Tasks aim to make long-running tool calls durable across disconnects and crashes. The proposed V2 removes session-heavy state, but polling scale and implementation complexity remain unresolved.",
  "summary": "MCP Tasks gives a long-running tool invocation a durable handle and lifecycle spanning working, input-required, completed, canceled, or failed states. **V1**, released as experimental in November, requires tasks to survive client, server, connection, and human delays.",
  "practical_implication": "If an agent launches work that may outlive a request, persist the task and design for retries, restarts, human input, and result recovery. The proposed **V2** moves toward a stateless core, removes task listing, and replaces long-session input handling with a client update endpoint.",
  "agent_context": "MCP Tasks gives a long-running tool invocation a durable handle and lifecycle spanning working, input-required, completed, canceled, or failed states. **V1**, released as experimental in November, requires tasks to survive client, server, connection, and human delays.\n\nIf an agent launches work that may outlive a request, persist the task and design for retries, restarts, human input, and result recovery. The proposed **V2** moves toward a stateless core, removes task listing, and replaces long-session input handling with a client update endpoint.\n\nV2 is described as cleaner but still involved, and the talk says it was expected in **July** rather than presenting a finalized release. Per-task polling also does not scale to millions of tasks; a notification mechanism was promising but unfinished.",
  "source": {
    "name": "AI Engineer",
    "url": "https://www.youtube.com/watch?v=s4r6nk5WsZw",
    "published_at": "2026-08-02T20:00:06.000Z"
  },
  "source_class": "video",
  "content_type": "Video",
  "layer": "context",
  "domains": [
    "coding"
  ],
  "topics": [
    "mcp",
    "tool-use",
    "agent-reliability"
  ],
  "verification": {
    "status": "source_linked",
    "label": "Source Linked",
    "method": "source_feed",
    "verified_at": null
  },
  "uncertainty": [
    "V2 is described as cleaner but still involved, and the talk says it was expected in **July** rather than presenting a finalized release. Per-task polling also does not scale to millions of tasks; a notification mechanism was promising but unfinished."
  ],
  "connected_context": {
    "meaning": "MCP Tasks defines durability as a protocol-level lifecycle rather than merely running work in the background. It clarifies the persistence, retry, recovery, cancellation, and human-input obligations behind long-running tools, while narrowing near-term adoption because V2 was not finalized and per-task polling still lacks a scalable replacement.",
    "corpus_size": 330,
    "generated_at": "2026-08-03T10:04:29.229Z",
    "connections": [
      {
        "title": "Expanding Managed Agents in Gemini API: background tasks, remote MCP and more",
        "source_name": "Google",
        "source_url": "https://blog.google/innovation-and-ai/technology/developers-tools/expanding-managed-agents-gemini-api/",
        "feed7_url": "https://feed7.dev/p/expanding-managed-agents-gemini-api-1idue29",
        "reason": "Gemini Managed Agents confirm demand for background execution, while MCP Tasks specifies additional lifecycle guarantees that asynchronous execution alone does not establish."
      },
      {
        "title": "Latest MCP spec now supported in mcp-handler",
        "source_name": "Vercel",
        "source_url": "https://vercel.com/changelog/latest-mcp-spec-now-supported-in-mcp-handler",
        "feed7_url": "https://feed7.dev/p/latest-mcp-spec-now-supported-in-mcp-handler-1kkt3s0",
        "reason": "The stateless 2026 protocol support aligns with MCP Tasks V2’s move toward a stateless core, while the migration requirements illustrate the compatibility cost of protocol evolution."
      },
      {
        "title": "Vercel MCP can now deploy code",
        "source_name": "Vercel",
        "source_url": "https://vercel.com/changelog/vercel-mcp-can-now-deploy-code",
        "feed7_url": "https://feed7.dev/p/vercel-mcp-can-now-deploy-code-1292qsq",
        "reason": "Deployment is a concrete long-running mutation that benefits from a durable task handle, especially because receiving an early URL does not prove the build completed successfully."
      },
      {
        "title": "MCP Apps: Extending the Frontier — Ido Salomon & Liad Yosef",
        "source_name": "AI Engineer",
        "source_url": "https://www.youtube.com/watch?v=-jY2T2PiJBE",
        "feed7_url": "https://feed7.dev/p/mcp-apps-extending-the-frontier-ido-salomon-liad-yosef-1gtlsr9",
        "reason": "MCP Apps could present task status or request human input, but MCP Tasks supplies the durable lifecycle underneath; the interactive view does not itself survive disconnects or restarts."
      }
    ]
  },
  "lifecycle": "Current",
  "published_at": "2026-08-02T20:00:06.000Z",
  "modified_at": "2026-08-02T20:00:06.000Z",
  "supersedes": [],
  "expires_at": null,
  "formats": {
    "html": "https://feed7.dev/p/mcp-tasks-async-why-aren-t-any-agents-supporting-them-cornelia-davis-tem-1fnlb47",
    "json": "https://feed7.dev/p/mcp-tasks-async-why-aren-t-any-agents-supporting-them-cornelia-davis-tem-1fnlb47.json",
    "markdown": "https://feed7.dev/p/mcp-tasks-async-why-aren-t-any-agents-supporting-them-cornelia-davis-tem-1fnlb47.md"
  }
}