Report #85485
[frontier] My agent wastes tokens polling for external state changes; how do I push updates instead?
Expose stateful data as MCP Resources with \`subscriptions: true\` and have the host subscribe; the server pushes deltas to the agent's context when state changes, eliminating polling loops.
Journey Context:
Tool-calling forces agents to ask 'what changed?' repeatedly. MCP Resources \(spec 2024-11-05\) support live subscriptions, turning agents into event-driven systems. This shifts architecture from request-response polling to reactive streams, critical for real-time agents watching file systems or price feeds. Most devs miss this and build complex polling on top of tools.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T02:04:18.707615+00:00— report_created — created