Bug
When a session is interrupted and restored from history, messages between a tool result and the subsequent assistant response can be lost. The user sees:
- The tail end of the last visible assistant message
- A "Session interrupted. Messages above were restored from history — some recent content may be missing." banner
- The next tool call shown as still "Running..."
Expected: All messages should be restored from history, preserving the full conversation flow.
Observed: Middle messages (between a Write tool completing and the assistant's follow-up analysis) were silently dropped. The conversation jumps from the tool execution to a later response with no indication of what was lost.
Repro
- Start a conversation with multiple tool calls and assistant responses
- Trigger a session interruption (e.g., network drop, app background)
- Restore the session
- Observe missing messages in the restored history
Screenshot
See .mitzo-images/image-1775840926380-0.png in the mgmt repo — shows the gap and "Session interrupted" banner.
🤖 Generated with Claude Code
Bug
When a session is interrupted and restored from history, messages between a tool result and the subsequent assistant response can be lost. The user sees:
Expected: All messages should be restored from history, preserving the full conversation flow.
Observed: Middle messages (between a Write tool completing and the assistant's follow-up analysis) were silently dropped. The conversation jumps from the tool execution to a later response with no indication of what was lost.
Repro
Screenshot
See
.mitzo-images/image-1775840926380-0.pngin the mgmt repo — shows the gap and "Session interrupted" banner.🤖 Generated with Claude Code