Todo list is not persisted when conversation is stopped or interrupted #15096

Description

The todo list (managed via the TodoWrite tool) is lost when a conversation is stopped or interrupted mid-session. On the web interface, the todo list remains visually present after interruption, but the agent no longer updates or reads it when the conversation resumes — the state is effectively stale/detached.

This is related to but distinct from #5934 (todo list lost after compaction) — the trigger here is a hard stop/interrupt rather than a compaction event.

Expected behavior:
The todo list persists across session interruptions and is restored/readable by the agent when the conversation resumes.

Actual behavior:
On the web UI, the todo list is still visible after interruption but is no longer read or updated by the agent — it becomes a stale display artifact with no functional backing state.

OpenCode version

No response

Steps to reproduce

1. Start a conversation on the web interface and have the agent create a multi-step todo list
2. Interrupt or stop the conversation before it completes
3. Resume the session
4. Observe that while the todo list may still be visible in the UI, the agent no longer reads or updates it

Screenshot and/or share link

No response

Operating System

Web

Terminal

No response