InMemoryTaskStore
AI overview
Sign in and the AI will write an overview from our coverage.
Headlines · 2
- Persistent MCP task stores can leave zombie tasks after restarts
A Juejin author built a file-based MCP TaskStore that persists each task as JSON and compared three restart policies after forcibly killing the service. The zombie policy left tasks reporting “working” until TTL expiry, fail marked them failed, and resume restarted work from the beginning without checkpoints, potentially repeating side effects. The article also recommends using lastUpdatedAt as a possible staleness signal and splitting long work into shorter tool calls where practical.
掘金 · 人工智能 · 🔥 0 - MCP task primitives tested in a note service
A hands-on report tests the MCP task primitives introduced in protocol version 2025-11-25: tasks/get, tasks/result, tasks/cancel and tasks/list. In the author’s note-service implementation, task creation returned in about four milliseconds and status updates arrived roughly once per second. The test also identified several operational issues: a client that had not called listTools() could silently fall back to synchronous execution; instance-local stores made tasks unavailable in a stateless setup; InMemoryTaskStore lost task data after a restart; and tasks/cancel changed task status without signaling the running background code. The report concludes that task primitives standardize how long-running tasks are invoked, while applications remain responsible for shared and durable storage, background execution and cancellation handling.
掘金 · 人工智能 · 🔥 0
Experience and discussion from the community
Share my InMemoryTaskStore experienceAsk about InMemoryTaskStore
Nobody has shared their experience with InMemoryTaskStore yet.