chat: mid-conversation context loss, undiagnosed #913

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

Reported from a real Telegram transcript (29 Jul, ~09:47 AEST / 23:47 UTC 28
Jul). Turn 3 of a coherent conversation was answered with a fresh greeting as
though no history existed; turn 4 was coherent again.

Ruled out by evidence:

  • Not two processes racing the bot token. docker compose ps on carina shows a
    single archied container.
  • Not a restart. That container had 43h uptime spanning the whole exchange.
  • Not history compression. DefaultCompressionConfig protects the first 3 and
    last 20 messages and triggers at 50% of a 128k window; there were three
    messages.
  • Not a canned greeting. No such string exists in the codebase, so the reply
    was model-generated from little or no history.
  • Not the session-key namespace split fixed in 96ab167: the deployed image
    predates the session lifecycle commands entirely.

Blocked on evidence, now unblocked: chat turns were completely unlogged (76
log lines covered two days, none a conversation). 96ab167 adds a "chat turn"
log line carrying session id, channel, thread and history depth.

Next step when it recurs: check the chat turn log for that message. A session
id differing from neighbouring turns points at key resolution (e.g. ThreadID
appearing on one message); history_messages of 0 or 1 with a stable session id
points at the store read path.

Do not close this by guessing. It needs one reproduction with the new log line.

Close reason

Confirmed fixed by Sam; no longer reproducible


Imported from beads archie-core-1786637499872-384-7952eb47 · GitHub #405 · type bug · priority P2 · created 2026-08-08 · closed 2026-08-17

Reported from a real Telegram transcript (29 Jul, ~09:47 AEST / 23:47 UTC 28 Jul). Turn 3 of a coherent conversation was answered with a fresh greeting as though no history existed; turn 4 was coherent again. Ruled out by evidence: - Not two processes racing the bot token. docker compose ps on carina shows a single archied container. - Not a restart. That container had 43h uptime spanning the whole exchange. - Not history compression. DefaultCompressionConfig protects the first 3 and last 20 messages and triggers at 50% of a 128k window; there were three messages. - Not a canned greeting. No such string exists in the codebase, so the reply was model-generated from little or no history. - Not the session-key namespace split fixed in 96ab167: the deployed image predates the session lifecycle commands entirely. Blocked on evidence, now unblocked: chat turns were completely unlogged (76 log lines covered two days, none a conversation). 96ab167 adds a "chat turn" log line carrying session id, channel, thread and history depth. Next step when it recurs: check the chat turn log for that message. A session id differing from neighbouring turns points at key resolution (e.g. ThreadID appearing on one message); history_messages of 0 or 1 with a stable session id points at the store read path. Do not close this by guessing. It needs one reproduction with the new log line. ### Close reason Confirmed fixed by Sam; no longer reproducible --- _Imported from beads `archie-core-1786637499872-384-7952eb47` · GitHub #405 · type bug · priority P2 · created 2026-08-08 · closed 2026-08-17_
sam added the mediumbug labels 2026-10-27 13:38:16 +00:00
sam self-assigned this 2026-10-27 13:38:16 +00:00
sam closed this issue 2026-10-27 13:38:16 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#913