Rockachopa/Timmy-time-dashboard
1
0
Fork 2
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

[matrix-qa] Chat messages silently dropped when WebSocket is offline — no user feedback #760

New Issue
Closed
opened 2026-03-21 18:05:43 +00:00 by Timmy · 0 comments
Timmy commented 2026-03-21 18:05:43 +00:00
Owner
Copy Link

Steps to Reproduce

  1. Load http://143.198.27.163/
  2. Type a message in the chat input at the bottom
  3. Press Enter or click the send button (>)

Expected

Either:

  • Message is queued and sent when connection is restored, OR
  • User sees a clear error like "Cannot send — you are offline" or the input is disabled

Actual

The message appears in the local chat panel as "YOU (offline): [message]" — which is good. However:

  1. The message is sent via bt() (WebSocket send) which silently fails because f (WebSocket) is null
  2. No toast/notification tells the user their message was NOT delivered to agents
  3. The "(offline)" suffix in the username is subtle and easy to miss
  4. Messages are lost forever — no queue/retry mechanism

Suggested Fix

  • Disable the send button or show a clear "OFFLINE" badge on the input bar when disconnected
  • Add a message queue that replays on reconnect
  • Consider a more prominent visual indicator (red border on input, disabled state)

Severity: P2

UX issue — users may think their messages were received when they were not.

## Steps to Reproduce 1. Load http://143.198.27.163/ 2. Type a message in the chat input at the bottom 3. Press Enter or click the send button (>) ## Expected Either: - Message is queued and sent when connection is restored, OR - User sees a clear error like "Cannot send — you are offline" or the input is disabled ## Actual The message appears in the local chat panel as "YOU (offline): [message]" — which is good. However: 1. The message is sent via `bt()` (WebSocket send) which silently fails because `f` (WebSocket) is null 2. No toast/notification tells the user their message was NOT delivered to agents 3. The "(offline)" suffix in the username is subtle and easy to miss 4. Messages are lost forever — no queue/retry mechanism ## Suggested Fix - Disable the send button or show a clear "OFFLINE" badge on the input bar when disconnected - Add a message queue that replays on reconnect - Consider a more prominent visual indicator (red border on input, disabled state) ## Severity: P2 UX issue — users may think their messages were received when they were not.
kimi added this to the Matrix Staging milestone 2026-03-21 20:24:28 +00:00
gemini was assigned by Rockachopa 2026-03-22 23:35:16 +00:00
gemini was unassigned by Timmy 2026-03-24 19:34:06 +00:00
Timmy closed this issue 2026-03-24 21:55:00 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
222-epic
Workshop: Timmy as Presence (Epic #222)
 actionable
Has a concrete code/config task extracted
 assigned-claude
Issue currently assigned to Claude agent — do not assign to another agent
 assigned-gemini
Issue currently assigned to Gemini agent — do not assign to another agent
 assigned-groq
assigned-kimi
Issue currently assigned to Kimi agent — do not assign to another agent
 assigned-manus
Issue currently assigned to Manus agent — do not assign to another agent
 claude-ready
consolidation
Part of a consolidation epic
 deprioritized
Keep open but not blocking P0 work
 deprioritized
Keep open but not blocking P0 work
 duplicate
Duplicate of another issue
 gemini-review
Auto-generated by Gemini, needs relevance review
 groq-ready
harness
Core product: agent framework, heartbeat, inference, memory
 heartbeat
Harness: Agent heartbeat loop
 inference
Harness: Inference and model routing
 infrastructure
Supporting stage: dashboard, CI/CD, deployment, DNS
 kimi-ready
Scoped and ready for Kimi to pick up
 memory-session
Harness: Memory and session crystallization
 morrowind
Harness: Morrowind embodiment
 needs-design
Needs architectural design before implementation
 needs-extraction
Philosophy with unextracted engineering work
 p0-critical
Priority 0: Must fix now
 p1-important
Priority 1: Important, next sprint
 p2-backlog
Priority 2: Backlog, do when time permits
 philosophy
Philosophical foundation — informs architecture decisions
 rejected-direction
Closed: rejected or superseded direction
 seed:know-purpose
Three Seeds: KNOW YOUR PURPOSE
 seed:serve-real
Three Seeds: SERVE THE REAL
 seed:tell-truth
Three Seeds: TELL THE TRUTH
 sovereignty
Harness: Sovereignty stack
No Label
Milestone
No items
No Milestone Matrix Staging
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok groq kimi manus perplexity Rockachopa
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#760
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?