{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreica4hxoj7ocxwinqsuvr6hp5zxvylx5l3w23huivcyhbd4h32uvtm",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mmqyhwidhpb2"
  },
  "path": "/t/wrong-tui-leaks-into-session/1381759#post_2",
  "publishedAt": "2026-05-26T11:34:42.000Z",
  "site": "https://community.openai.com",
  "textContent": "I am not OpenAI staff, but this sounds like a state/routing bug between active Codex CLI sessions rather than a task failure.\n\nA few details would make it easier to reproduce: Codex CLI version, terminal app, OS, whether both sessions were started from the same repo/worktree, and whether the error appears after resuming a thread or while both sessions are live.\n\nA minimal repro would be especially useful: start session A, start session B, leave both running, then note which keypress/action causes prompts from B to appear in A. Since you said the background tasks keep running, I would include that too, because it separates UI/session routing from agent execution.\n\nFor now, I would avoid running multiple TUI sessions in the same terminal/tmux context and use separate terminal windows or worktrees when possible.",
  "title": "Wrong TUI leaks into session"
}