{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreib2lxvnqb2ce57ed3cyjlhfbnl4xoxpwrjdvgqe4nukq63ntc5cka",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mibojg6rcpe2"
  },
  "path": "/t/chatgpt-mcp-apps-bridge-drops-custom-meta-from-tool-results-in-ui-notifications-tool-result/1378047#post_2",
  "publishedAt": "2026-03-30T12:02:34.000Z",
  "site": "https://community.openai.com",
  "tags": [
    "Bug Report: ChatGPT strips _meta from tool results and breaks MCP Apps viewUUID state persistence pattern",
    "ChatGPT Apps SDK",
    "MCP Apps compatibility guide",
    "documented viewUUID pattern for persisting view state"
  ],
  "textContent": "Same here.\n\nRaised it almost a month ago, no response.\n\nBug Report: ChatGPT strips _meta from tool results and breaks MCP Apps viewUUID state persistence pattern ChatGPT Apps SDK\n\n> We migrated our ChatGPT App from the OpenAI Apps SDK to the MCP Apps standard, following the MCP Apps compatibility guide. The migration went fine. Tools, resources, ontoolresult, callServerTool, sendMessage, and app-only tool visibility all work correctly. However, when implementing the documented viewUUID pattern for persisting view state, we discovered that ChatGPT strips _meta from tool results before forwarding them to the widget. Steps to reproduce Server returns _meta: { viewUUID: cryp…",
  "title": "ChatGPT MCP Apps bridge drops custom _meta from tool results in ui/notifications/tool-result"
}