telegram: the live-edit answer keeps its turn-start timestamp and can sort before the conversation #1077

Closed
opened 2026-10-27 13:38:56 +00:00 by sam · 0 comments
Owner

The final reply is delivered by editing the message created at the first streamed frame, and editMessageText does not change the message date — so a long tool-using turn's answer is timestamped at turn start, can predate messages sent during the turn, and sorts before the conversation that produced it. Cosmetic and inherent to the watch-the-answer-being-written design (delete-and-resend would flicker and reorder), but it is a visible consequence nothing documents or tests.

Failure: a turn with a two-minute tool phase produces an answer whose timestamp precedes a follow-up user message that references it; chat history ordering places the answer before the conversation that produced it.

Design

Either accept and document the limitation (a comment on liveReply/finalize), or investigate a delete-and-resend on finalize for turns that cross a meaningful time gap. Low priority; a documentation note may be the right fix.

Acceptance criteria

The timestamp behavior is at least documented (or changed and tested), so it is a known trade-off rather than a surprise.

Close reason

Documented the accepted trade-off on liveReply's doc comment per the design note's preferred option; no behavior change. Committed ed18bfb.


Imported from beads archie-core-52f7 · GitHub #495 · type task · priority P4 · created 2026-08-14 · closed 2026-08-14

The final reply is delivered by editing the message created at the first streamed frame, and editMessageText does not change the message date — so a long tool-using turn's answer is timestamped at turn start, can predate messages sent during the turn, and sorts before the conversation that produced it. Cosmetic and inherent to the watch-the-answer-being-written design (delete-and-resend would flicker and reorder), but it is a visible consequence nothing documents or tests. Failure: a turn with a two-minute tool phase produces an answer whose timestamp precedes a follow-up user message that references it; chat history ordering places the answer before the conversation that produced it. ### Design Either accept and document the limitation (a comment on liveReply/finalize), or investigate a delete-and-resend on finalize for turns that cross a meaningful time gap. Low priority; a documentation note may be the right fix. ### Acceptance criteria The timestamp behavior is at least documented (or changed and tested), so it is a known trade-off rather than a surprise. ### Close reason Documented the accepted trade-off on liveReply's doc comment per the design note's preferred option; no behavior change. Committed ed18bfb. --- _Imported from beads `archie-core-52f7` · GitHub #495 · type task · priority P4 · created 2026-08-14 · closed 2026-08-14_
sam added the task label 2026-10-27 13:38:56 +00:00
sam self-assigned this 2026-10-27 13:38:56 +00:00
sam closed this issue 2026-10-27 13:38:56 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1077