Repository navigation
Replies: 1 comment
|
This switch is explained by the current completion handler. At There is already a relevant precedent. The resume path checks that the source session is still selected before applying completion. In an isolated check of these extracted functions with API and UI stubs, the direct path left B for A's result both with and without a new continuation ID, while the resume path preserved B. This was not a live browser test. For a focused fix, keep the source session ID separate from the returned continuation ID and gate visible transcript, status and navigation updates on whether the source is still selected. Following the continuation while A remains selected should still work. The error and cleanup paths also need that ownership check so A's completion cannot clear B's busy state. Maintainers would need to confirm the intended behavior, but the existing resume guard supports the distinction you describe. |
Uh oh!
There was an error while loading. Please reload this page.
I noticed this behavior while using the WebUI:
Is this intentional, or should the WebUI preserve the conversation the user has since selected?
I understand that compression may create a continuation session, and following that continuation makes sense while I am still viewing A. My question is specifically about switching away from an unrelated conversation B.
My preference would be to update A’s compression status in the background without changing the active conversation. If the current behavior is unintended, I would be happy to help prepare a focused fix and regression test.
All reactions