Resolved comment threads now stay honest
A resolved comment thread could keep showing as resolved even after a new reply landed in it; it now reopens automatically when that happens.
Summary
A resolved comment thread used to stay marked resolved even after someone replied into it, so a thread could show a green check while an unanswered question sat right underneath it. Replying to a resolved thread now reopens it automatically.
What You Gain
A "resolved" marker is only useful if it means the conversation is actually settled. When a new reply could sit unnoticed under a stale resolved marker, the signal stopped being trustworthy — you had to open every thread to be sure nothing was waiting on you.
Now a thread also holds at most one resolved marker at a time, so two different people resolving the same discussion at different times can't leave it carrying two conflicting markers. Each resolution also records who resolved it.
How It Works
- Replying to a resolved thread reopens it automatically.
- A thread can carry only one active resolution; resolving a comment clears any other resolution already on that thread.
- It's worth knowing that resolving a thread is a marker for people only — it does not start, restart, or stop an agent. Mention the agent directly in a new comment when you want it to act.
Where to Find It
This applies automatically to every comment thread, on every task.
See what else shipped this month on the Effigate Command Center changelog, or try Effigate Command Center with your own team.