Occasional mild amnesia on queued chat messages

[ammario]

I've noticed some mild amnesia when a queued message is sent at the end of a tool call. For example:

User: Begin working on Task 1
Model: essentially completes task 1
User (interrupted): also do Task 2
Model: starts doing task 1 from scratch and also task 2

It seems to get to the right result at the end, but the model gets very confused that much of task 1 was already complete. I wonder if there's more to learn from Claude Code.

[ammario]

cc @ethanndickson

This was an issue before your changes as well. We've never had truly great interruptions.

[ethanndickson]

Should be fixed by #807, but won't close this issue until we know for sure. There might be other improvements to make as well, after I snoop on Claude Code a bit.

[ammario]

Kk. We may want to design the partial system to avoid "flushing", instead using a WAL-like pattern so that messages are immediately committed to disk. I think I did flushing at first because the system overwrites the whole partial file on each flush, which would be inefficient to do real-time.

Many amnesia issues have arisen due to the async flushing behavior though.

[ammario]

Saw this in my logs:

Error reading partial: SyntaxError: Unexpected end of JSON input
    at JSON.parse (<anonymous>)
    at PartialService.readPartial (/Users/ammar/Projects/coder/mux/src/node/services/partialService.ts:52:28)
    at PartialService.commitToHistory (/Users/ammar/Projects/coder/mux/src/node/services/partialService.ts:124:21)
    at AgentSession.streamWithHistory (/Users/ammar/Projects/coder/mux/src/node/services/agentSession.ts:405:26

which is almost certainly related! #826 will help.