Hey there !
We’ve noticed this morning that all apps on OpenAI now fail to access toolInput, toolOutput and toolResponseMetadata host context provided values using the former Apps SDK methods (window.openai). This despite tool call being successful and injected in context.
Do you know anything about this issue ?
Hydratation through MCP App JSON-RPC messages is working fine though
Hey, it looks like window.openai.toolInput still gets hydrated in some context. Here are 2 screenshots from 2 apps currently published in ChatGPT app store. One receives values in window.openai, the other doesn’t (or at least just for tool, the displayMode always gets hyrdated).
Any idea what might be the reason for this difference?
My best guess is some coupling between MCP App and Apps SDK (like waiting for a ui/initialize message to hydrate window.openai properties?)
We’ve been able to narrow this down to when openai/outputTemplate and ui.resourceUri coexist on a tool. Still investigating.
Fix should be out in the next deploy, please let me know if you run into this further!
Thanks for deploying a fix @casey-chow ! Confirmed the affected apps now work correctly. We’re working on removing openai/outputTemplate property from Skybridge apps (that were affected by this issue) in order to always rely on ui.resourceUri instead