Hey, thanks for the report. I can see the screenshot with the toast Failed to open resource: ui://widget/openai/confluence-widget.html.
What’s happening here: resources like ui://widget/... are MCP App widgets (text/html;profile=mcp-app), not regular files. They’re meant to render inline in the chat after a tool call, not to be opened as a file in the editor. In the Glass agent window, trying to open this kind of resource fails, which is why you see that error. In the editor window, the open flow works differently right now, so it doesn’t crash there.
Important note: this doesn’t affect Atlassian (Jira/Confluence) tool calls themselves. Only the attempt to open the widget resource as a file is broken.
I’ve reported this internally. I can’t share an ETA yet, but I’ll post an update in the thread as soon as I have one.
We’ve made a number of improvements to how MCP widget resources work in the agent window since you posted! Resources like the Confluence widget now render inline in the chat instead of being opened as a file. Could you give it another try on the latest version?
In the agent window, use the Atlassian plugin and run a tool call that returns a Confluence/Jira widget
The widget should render inline in the conversation instead of showing the “failed to open resource” error
If you still can’t view the widget content on the latest version, please share updated details so we can take a fresh look!
