Chat UI: messages show no timestamps — render per-message time (HH:MM local, full on hover, day separators) #29

New issue

Open

opened 2026-10-29 21:15:08 +00:00 by heike · 0 comments

heike commented

2026-10-29 21:15:08 +00:00

Member

Requested by Felix (manager), 2026-10-30: timestamps in the chat UI.

Current behavior (verified in code, ChatPane.jsx message render): each message renders exactly two things — sender display name and body. The ts field exists on every message document but is never displayed. The UI gives no way to tell when anything was said.

Why it bites in practice:

Multi-participant conversations (humans + agents) arrive interleaved; without timestamps you cannot reconstruct the order of a back-and-forth beyond the visual list position.
It materially slowed debugging of #23 (delayed own-message echo): "appeared 10 minutes later" was only observable against a wall clock, not against the data — the message's ts said the truth the whole time, invisibly.
For agents working long turns, seeing when a message landed is the difference between "just replied" and "stale instruction".

Proposed shape (minimal, PROPOSED — styling/details for whoever picks it up):

Per-message time, browser-local, HH:MM.
Full timestamp + date on hover (title attribute) for copy-paste into issues.
Day separator when the date changes within a conversation.
Keep it quiet visually: dimmer than the sender name, no per-message chrome.

Filed by heike. Small, self-contained; good first web PR.

**Requested by Felix (manager), 2026-10-30: timestamps in the chat UI.** **Current behavior (verified in code, ChatPane.jsx message render):** each message renders exactly two things — sender display name and body. The `ts` field exists on every message document but is never displayed. The UI gives no way to tell *when* anything was said. **Why it bites in practice:** - Multi-participant conversations (humans + agents) arrive interleaved; without timestamps you cannot reconstruct the order of a back-and-forth beyond the visual list position. - It materially slowed debugging of #23 (delayed own-message echo): "appeared 10 minutes later" was only observable against a wall clock, not against the data — the message's `ts` said the truth the whole time, invisibly. - For agents working long turns, seeing when a message landed is the difference between "just replied" and "stale instruction". **Proposed shape (minimal, PROPOSED — styling/details for whoever picks it up):** - Per-message time, browser-local, `HH:MM`. - Full timestamp + date on hover (title attribute) for copy-paste into issues. - Day separator when the date changes within a conversation. - Keep it quiet visually: dimmer than the sender name, no per-message chrome. Filed by heike. Small, self-contained; good first web PR.