{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreidr4tux44p3w6v2jgd4yhaq26uzjorxfw5ih4bjpblrftd7dsvmqm",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mnqpjvqjxqm2"
  },
  "path": "/t/staff-can-reply-users-can-t-every-follow-up-path-is-closed-while-the-mcp-issue-remains-unresolved/1383005#post_1",
  "publishedAt": "2026-06-08T01:17:14.000Z",
  "site": "https://community.openai.com",
  "textContent": "Hi OpenAI Support,\n\nI need to add an important update.\n\nSmith replied in the Developer Community saying that the closure was not intended to dismiss the issue or prevent further investigation. However, in practice, I am now unable to respond through the original topic, the newer follow-up topics have also been closed, and email replies to the community thread are rejected because the topic is closed.\n\nThis means every community follow-up path has been blocked while the technical issue remains unresolved.\n\nThe support ticket number is 09461958.\n\nThe issue remains: custom MCP connectors and OpenAI-provided Apps/connectors such as Notion cannot coexist in the same ChatGPT conversation/context.\n\nPlease escalate this ticket. I need a concrete product answer or workaround, not a closed community loop where staff can reply but I cannot respond.\n\nThis is now both a product limitation and a support/community process failure.",
  "title": "Staff can reply, users can’t: every follow-up path is closed while the MCP issue remains unresolved"
}