Before submitting
Area
apps/web
Steps to reproduce
- Ask an agent to review some code
- Come back to the thread 15 minutes later to find it has been marked as settled
Expected behavior
A thread should not be automatically marked as settled until the seven days, as is in my settings, has passed, or if marked as settled manually.
Sidenote - it would be great to have a command palette option and/or a key binding to toggle a thread's settled status.
Actual behavior
Example image below:
Threads are being marked as settled - I only had the one thread going at the time so it wasn't a big deal but a thread could get lost in the ether by this behaviour.
The first time this happened I thought I must have clicked on the settle thread by mistake, but it has happened multiple times since then.
Impact
Minor bug or occasional failure
Version or commit
No response
Environment
macOS latest
Logs or stack traces
Screenshots, recordings, or supporting files
SCR-20260729-llzm.png
Workaround
Manually check settled threads to ensure nothing has ended up there that shouldn't have been
Before submitting
Area
apps/web
Steps to reproduce
Expected behavior
A thread should not be automatically marked as settled until the seven days, as is in my settings, has passed, or if marked as settled manually.
Sidenote - it would be great to have a command palette option and/or a key binding to toggle a thread's settled status.
Actual behavior
Example image below:
Threads are being marked as settled - I only had the one thread going at the time so it wasn't a big deal but a thread could get lost in the ether by this behaviour.
The first time this happened I thought I must have clicked on the settle thread by mistake, but it has happened multiple times since then.
Impact
Minor bug or occasional failure
Version or commit
No response
Environment
macOS latest
Logs or stack traces
Screenshots, recordings, or supporting files
SCR-20260729-llzm.png
Workaround
Manually check settled threads to ensure nothing has ended up there that shouldn't have been