{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreigwnottvj4fvovj3bhcj2g3dwkancw7thse73nged5isbonrfqwgm",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mmrfvz4x6fu2"
  },
  "path": "/t/wrong-tui-leaks-into-session/1381759#post_4",
  "publishedAt": "2026-05-26T15:35:14.000Z",
  "site": "https://community.openai.com",
  "textContent": "Possible technical cause of the “wrong TUI leaks into session” bug:\n\n  * PTY/shared terminal sessions not fully isolated\n  * stdout/stderr streams multiplexed incorrectly\n  * incorrect reuse of session_id or websocket state\n  * race conditions during session attach/detach\n  * cached UI state not reset when switching agent/session\n  * possible cross-talk between TUI renderer and backend event bus\n\n\n\nThings worth checking:\n\n  * strict per-PTY isolation\n  * full cleanup on disconnect\n  * renderer state invalidation\n  * strong binding between user/session/terminal\n  * locking around concurrent streams\n  * separate namespaces for TUI state\n\n\n\nThis looks more like a session orchestration issue than an AI model issue itself.",
  "title": "Wrong TUI leaks into session"
}