Reset todos window to the beginning when doing another task, after the task is completed

[erelst]

In the same session, the "todos" or window on the right in the screenshot (which contains confidence scores, etc.) doesn't change at all even if I perform other tasks. If the previous task is completed, shouldn't those todos be replaced with the todos from the current task? I've done many different tasks and sometimes I see in thinking/reasoning that there are actually new todos running, but the todos window on the right still displays the ones from the initial task of the session. Actually I'm confused whether this is a feature request or a bug, please check it.

[1jehuang]

It was a bug, thanks for flagging it. The goal assessments (confidence panel) are deliberately retained when a todo write does not mention them, so a partial update cannot erase them, but nothing pruned goals whose todo group had already disappeared. Goals from your first task therefore stayed visible after the list moved on.

Fixed in #701: goals whose group no longer exists in the current todo list are dropped, while goals-only writes and flat (ungrouped) lists are unaffected. If you still see stale entries after that lands, please reopen with a screenshot.

--- — Jcode agent (automated triage), on behalf of @1jehuang

[1jehuang]

Update: the fix is merged to master (#701). Follow-up end-to-end tests are in #702. It will ship in the next release.

--- — Jcode agent (automated triage), on behalf of @1jehuang

[1jehuang]

One more finding while verifying this, worth flagging because it can produce the same symptom through a different path.

There is a second mechanism: when a single todo write both creates and completes a group without an end_to_end_ownership score, the ownership quality gate rejects the entire write and the previously stored todo list is kept. I confirmed this against the real tool: after such a write the stored todos still describe the previous task, so the panel looks frozen even though the agent moved on.

That gate is deliberate design (it is what forces the agent to validate before declaring a group done), so I have not changed it. Leaving it for @1jehuang to decide whether a rejected write should still be visible somehow, for example by surfacing the rejection in the panel instead of silently keeping stale content.

The goal-retention half of this issue is fixed and merged.

--- — Jcode agent (automated triage), on behalf of @1jehuang