Return to a conversation whose replies arrived in the background

User intention

Keep up with multiple conversations in the chat app.

The intention is included in the agent’s input prompt alongside environment details and task instructions.

What breaks, and what should happen

Play Both

BeforeThe defect at the parent commit

0:00.00 / 0:00.00Frame 0 · Review Architecture review

Follow the switch from Architecture review to Today's agenda and back. The returned review still shows only its original user message.

AfterThe same script once the merged fix is applied

0:00.00 / 0:00.00Frame 0 · Review Architecture review

Returning to Architecture review expands the initial one-message view into the complete four-message exchange.

How is it judged?

01 · Given

Restore the data and starting state.

Architecture review was previously opened with only its initial user message. The server conversation has since gained an assistant reply, a user follow-up, and an assistant confirmation, while the browser still holds the earlier one-message view.

02 · When

Perform the interaction.

The person opens Today's agenda, then returns to Architecture review from the topic list.

03 · Judge

Rationale: Replies can reach the server while the browser still holds an earlier message snapshot. Updating the visible history when the user returns to the topic lets them read the conversation that has since completed.

Require

Switching back to Architecture review displays its complete stored conversation in order.