Repository navigation
Chat messages disappear and timeline shows empty conversation #27704
Description
What happened
The user reports: "chats dont show messages at all". A screenshot shows an otherwise blank chat with the text "Send a message to start the conversation." The user also reports that they cannot see the triage agent's replies.
Diagnosis
Cause not established. The local database contains message records for 484 non-deleted v2 threads, including this triage thread. This does not establish which thread was visible in the screenshot or prove every affected message is intact. The matching build's MessagesTimeline renders the displayed placeholder when its timeline rows are empty and several other empty-state conditions hold. Why the affected client has no visible messages is unknown. Recent server trace entries contained no recorded failure exits; no client console trace was available.
Steps to reproduce
- Open a chat with prior messages in T3 Code.
- The user reports that messages do not appear and supplied a screenshot of the empty-conversation placeholder.
The trigger, whether every chat is affected, and a deterministic reproduction are not yet known.
Version
Version where the screenshot was taken: unknown. The triage session was launched from desktop nightly 0.1.6-nightly.20261030.3917; its local server reports the same version, commit 97e35bcf23e4dcf34c2dcffadd37c08db0e01e52. The user has not confirmed whether the screenshot shows this build or another surface.
Environment
Triage machine: macOS arm64, Darwin 27.2.0, Node 24.22.1. Surface of the affected chat is unconfirmed.
Evidence
- Screenshot shows:
Send a message to start the conversation. - A read-only database query found message records for 484 non-deleted v2 threads.
- The recent server trace had no spans with a failure or defect exit.
- In the matching server source,
apps/web/src/components/chat/MessagesTimeline.tsxdisplays that placeholder whenshowsEmptyStateis true; its conditions includerows.length === 0.
Related issues
#22216 also involved apparently missing history on Mac nightly, but concerned connection-catalog decryption and missing projects; there is no evidence of that cause here. No confirmed duplicate identified.
Fix applied or workaround
The user confirmed that messages returned after quitting and reopening T3 Code. Restarting is a workaround for this occurrence; the underlying cause remains unknown. No database changes were made.
Filed by
GPT-6.1 Terra through the Codex harness via T3 triage.
Activity
imCinq commentedon Oct 30, 2026
not sure what else to say, it just doesn't work and GPT couldn't find a reason why
lstanden commentedon Oct 30, 2026
Have the same thing happening to me on MacOS. I'm waiting for my currently working agent threads to finish so I can restart and not lose progress.
rebelonion commentedon Oct 30, 2026
Seeing the same thing on Linux 7.2.11-arch1-1
Quitting and reopening fixes it until I start a new chat
lstanden commentedon Oct 30, 2026
Follow-up: confirmed that Command-R fixes the empty conversation on macOS without quitting or restarting the app, so I can keep my background agent threads running.
This seems to recur across all newly created threads for me. Refreshing restores the messages, and the backend was still able to return them while the UI was blank. That points toward a frontend state/loading issue, though I haven't established the root cause.
Observed on T3 Code Nightly
0.1.6-nightly.20261030.3917.imCinq commentedon Oct 30, 2026
Were you guys just quiet about this? This has been happening to me for over 24 hours and no issue, so I finally made one and people are replying. 😭
willadamskeane commentedon Oct 30, 2026
Same thing is happening to me.
lstanden commentedon Oct 30, 2026
I think it's just that I updated at the start of my workday here, so I only just started seeing it.
rebelonion commentedon Oct 30, 2026
Related issues: #27641, #27443 / #27615 / #27623
ranjithkt commentedon Oct 30, 2026
Yes same thing happening to me as well.
lstanden commentedon Oct 30, 2026
It looks like the man, the myth,
the person who apparently never sleepsthe legend has already resolved this, and a new release just landed 🫡🔗 #27522
My bug report was outdated before I finished typing it.
imCinq commentedon Oct 30, 2026
It's quite odd. I'm on the latest release.
t3dotgg commentedon Oct 31, 2026
Note
🤖 Claude Opus 5.5 responding on behalf of Theo
Closing: this is covered by #27522, which landed. Reopen if an important part is still missing.