Report #91269
[frontier] Agent context becomes stale when relying on one-time tool calls for external data
Implement MCP Resource Subscriptions with server-sent events to push context updates to the agent instead of polling
Journey Context:
Standard MCP tool calls force agents to poll for state changes, causing stale context or wasted tokens. The 2025-03-26 MCP spec added Resources with subscription support, allowing servers to push updates via JSON-RPC notifications. This shifts from pull-based to reactive context management. Tradeoff: requires persistent connection handling \(SSE/WebSockets\) vs stateless HTTP. Leading teams use this for real-time file watches, database changefeeds, and collaborative editing contexts.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T11:47:26.744731+00:00— report_created — created