Separate incoming updates from agent workYou treat delivery and model execution as separate decisions. A resource subscription receives updates but never grants an agent permission to run.rustacademyacademy/topics/notifications-vs-subscriptionswebsite/content-src/academy/course.mjsacademySeparate incoming updates from agent work
You treat delivery and model execution as separate decisions. A resource subscription receives updates but never grants an agent permission to run.
7 focused minutesNot started
Unit example (nearest native match)
See the idea in context
let transport = AxMCPStreamableHTTPTransport::new(
let mut source = AxMCPEventSource::with_policy(
AxMCPResourceSubscriptionPolicy::All,
source.start()?;
source.poll();
Discover the endpoint
The live catalog identifies concrete resources and supported event capabilities.
Apply subscription policy
Your application chooses which updates it actually wants.
Route through the inbox
An explicit event route decides whether the update only records state or wakes work.
Run itIn your own project
cargo add axllm
use axllm::{ai, ax};
use serde_json::json;
let llm = ai("openai", json!({"apiKey": std::env::var("OPENAI_API_KEY")?}))?;
let classify = ax("review:string -> sentiment:class \"positive, negative, neutral\"")?;
Set OPENAI_APIKEY in your environment before running provider-backed code.
In the ax repo
From a clone of the ax repo:
npm run example -- rust src/examples/rust/mcp/resource_wake_agent.rs