English(EN) How do I give my LLM workflow persistent context across independent client connections?

MCP 协议转向基于身份的上下文，实现持久化 LLM 工作流

作者 PulseAugur 编辑部 · [1 个来源] · 2026-10-04 23:00

MCP 协议已更新，移除了会话 ID，将基于连接的上下文切换为基于身份的上下文。此更改意味着上下文不再与特定的客户端连接绑定，而是存储在外部，并通过稳定的身份（如用户或项目）进行访问。这使得工作流能够在独立的客户端连接之间保持持久化上下文，即使这些连接由不同的服务器实例处理或相隔数小时。 AI

影响通过将上下文与瞬时连接分离，实现了更健壮和持久化的 LLM 工作流。

排序理由协议规范更新，详细说明了上下文管理的变化。[lever_c_demoted from research: ic=1 ai=1.0]

AI 生成摘要 · Google Gemini · 来自 1 个来源。我们如何撰写摘要 →

本文如何被排名

Signal score: 21 / 100; Composite score across the factors below. Higher = stronger signal that this story matters right now.
Newsworthiness bucket: Tool; 协议规范更新，详细说明了上下文管理的变化。[lever_c_demoted from research: ic=1 ai=1.0]
Source corroboration: Single-source cluster; Only one publisher covered this so far. Single-source stories can still rank when the publisher is high-authority, but they lack cross-source corroboration.
Topics: infra; Editorial topic classification. Feeds into how the story surfaces on /topic/<slug> hub pages and into the per-entity coverage mix.
AI-industry relevance: High; Clearly on-topic for AI-industry coverage.
Story freshness: Breaking (< 6h); Fresh story with cross-source coverage still developing. Ranking may shift as more sources report.

完整方法见我们的编辑标准。

dev.to — MCP tag TIER_1 English(EN) · Edward Izgorodin · 2026-10-04 23:00

如何为我的LLM工作流在独立的客户端连接之间提供持久化上下文？

<p>You build a support workflow in two steps. At 06:00 a scheduled job connects to your MCP server, reads the night's tickets and works out that 4127 and 4133 are the same bug. At 10:00 you open a chat client and ask the agent which tickets can be closed. That is a new client con…