this is an evolution of the experimental context in ai sdk 6. it is separated by tool and different from runtimeContext for security reasons (to prevent malicious 3rd party tools from stealing sensitive context)

Mastra 1.0 [beta] is just perfect for building Slack agents! Slack is built for business-specific agents: ❇️ they live where the team works ❇️ they keep everyone synced ❇️ they distribute knowledge timely The hardest part in Slack is orchestrating memory around Slack primitives: 🔼 channel 🔼 thread 🔼 user 🔼 team Can pretty tricky: make one mistake → your agent will become incoherent or harmful. Mastra gives you super granular control over [memory ←→ primitive] config for all three memory types: ❇️ Conversational [short-term, sliding window] ❇️ Semantic [snippets from previous threads] ❇️ Working [user preferences, persistent] And there is more: RequestContext [ex RuntimeContext] It allows you to dynamically & predictably inject dynamic context: 📅 dates 🕒 events 📍 location-specific updates and so on... Slack agent easily adapts to Bob from sales in SF and Jen from client service in NY Mastra is the first framework I've used that makes building Slack agents a nice DevExp. This feature [↓] is next level: 3-click Slack deploy🔥 Now you can skip app manifest/tokens/keys [I assume] Mastra gives you Slack-native memory config right away. Setting up all these can be demoralizing if you new to this. Now you can deploy your Slack agent fast, test it, use it. And go to the technical stuff when you get the base orchestration right. Just 💎

为什么OpenAI这么执着于 tool as ui, 而不是 agent as ui？ 今天把openai的app sdk的开发文档指引读了一遍，整体上跟之前看过的开源mcp-ui项目很像，只是在mcp-ui的基础上增加了design standard和runtimecontext standard，但是仍然是tool as ui的方向（tool = widget )，也正是因为这个基础，所以openai的design standard里更推荐的是single-shot viewer，而非 multiturn editor； 但是仔细看日常的每个long time work，个人认为基于agent这种multiturn的artifact似乎更加合理一些？比如一个codebase scope agent artifact, 一个slide scope agent artifact，一个canvas scope agent artifact，但是这么做就弱化了模型的重要性，所以openai想成为AI OS bridge而选择这个路径，也是可以理解的

Now that you mention it...ApplicationContext is right along the lines of what I had in mind. Other frameworks refer to it as RuntimeContext. What I might want to do is attach the event emitter to this object to make it more well-structured.