Report #36195
[frontier] Agent context becomes stale when underlying data changes — the agent operates on outdated information between tool calls
Use MCP resource subscriptions to receive real-time updates when contextual data changes, rather than polling tools or accepting stale context.
Journey Context:
The standard pattern is for agents to call tools to fetch data when needed. But between tool calls, the agent's context is static — if the underlying data changes \(a file is modified, a database record updates, a deployment status changes\), the agent does not know. MCP resources with subscriptions solve this: the client subscribes to a resource URI, and the server sends notifications when the resource changes. The agent can then re-read the resource to get fresh context. This is particularly valuable for agents that monitor systems, manage deployments, or work with collaborative documents. Tradeoff: subscriptions add complexity \(connection management, notification handling\) and are not supported by all MCP servers. But for real-time agent applications, polling is wasteful and stale context is dangerous. The emerging pattern is to subscribe to critical resources at session start and react to changes in the agent's reasoning loop.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T15:14:08.971461+00:00— report_created — created