Reproduced on Linux web in Chrome against main 70e5e384da, using an isolated dev database. Enabled in-app notifications, completed a Codex turn while viewing another thread, then opened the completed thread through its sidebar row. The route changed to that thread while its completion toast remained visible.
Thread done toast stays open after opening that thread without the toast button#20883
When a "Thread completed" (or input/approval) toast appears and I open that same thread some other way, for example with keyboard navigation or the sidebar, the toast stays on screen. It only closes through its own "Open thread" button or its timeout.
Expected: once the thread is open, its toast is no longer useful and should close.