You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Threads are getting auto-settled minutes after completion #4811
I searched existing issues and did not find a duplicate.
I included enough detail to reproduce or investigate the problem.
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.
Activity
HemalR commentedon Jul 30, 2026
I haven't been able to replicate this after the last update - going to assume it has been fixed 👍