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

[Infra] Message queue / offline buffer for Workshop panel #913

New Issue
Closed
opened 2026-03-22 13:24:01 +00:00 by Timmy · 2 comments
Timmy commented 2026-03-22 13:24:01 +00:00
Owner
Copy Link

Problem

When the Hermes API backend is unreachable (Mac offline, VPS restart, network blip), messages sent from the Workshop panel are lost. The user gets no feedback, and Timmy never sees the message.

Solution

Add an offline message queue so that:

  1. Frontend (panel.js): If the API returns an error or times out, store the message in localStorage with a timestamp
  2. Frontend retry: On reconnection (periodic health check), replay queued messages in order
  3. VPS-side queue (optional): nginx or a small service buffers POST requests when upstream is down, replays when it comes back
  4. User feedback: Show "queued" status on messages that haven't been delivered yet, with a visual indicator

Scope

  • Add localStorage message queue in panel.js
  • Add connection health check (ping endpoint every 30s)
  • Show queued/delivered/failed status per message
  • Replay queued messages on reconnection
  • Optional: VPS-side queue service (Redis or SQLite buffer)

Priority

High — complements the VPS migration. Even with Hermes on VPS, there will be restarts and brief outages. Messages should never be silently lost.

## Problem When the Hermes API backend is unreachable (Mac offline, VPS restart, network blip), messages sent from the Workshop panel are lost. The user gets no feedback, and Timmy never sees the message. ## Solution Add an offline message queue so that: 1. **Frontend (panel.js):** If the API returns an error or times out, store the message in `localStorage` with a timestamp 2. **Frontend retry:** On reconnection (periodic health check), replay queued messages in order 3. **VPS-side queue (optional):** nginx or a small service buffers POST requests when upstream is down, replays when it comes back 4. **User feedback:** Show "queued" status on messages that haven't been delivered yet, with a visual indicator ## Scope - [ ] Add `localStorage` message queue in `panel.js` - [ ] Add connection health check (ping endpoint every 30s) - [ ] Show queued/delivered/failed status per message - [ ] Replay queued messages on reconnection - [ ] Optional: VPS-side queue service (Redis or SQLite buffer) ## Priority **High** — complements the VPS migration. Even with Hermes on VPS, there will be restarts and brief outages. Messages should never be silently lost.
claude was assigned by Rockachopa 2026-03-22 23:31:57 +00:00
perplexity commented 2026-03-23 13:53:07 +00:00
Collaborator
Copy Link

📋 Triage: Infrastructure — Deprioritized

Dashboard/UI layer. The harness is the product — dashboard work is secondary.

Ref: #1076

📋 **Triage: Infrastructure — Deprioritized** Dashboard/UI layer. The harness is the product — dashboard work is secondary. Ref: #1076
claude added the deprioritizedinfrastructure labels 2026-03-23 13:56:21 +00:00
claude commented 2026-03-23 22:10:23 +00:00
Collaborator
Copy Link

PR created: #1205

Implemented the full frontend offline queue:

  • queue.js: New localStorage-backed queue with QUEUED/DELIVERED/FAILED status and 24h auto-expiry
  • state.js: 30-second health-check polling /api/matrix/health, WebSocket auto-reconnect, onConnectionChange listener
  • index.html: Job submissions now queue on network failure (instead of fake-success); queued jobs replay automatically on reconnection; amber pulsing badge shows pending count across page loads
  • style.css: Queued state panel with clock icon and amber palette

VPS-side queue (Redis/SQLite buffer) was marked optional in the issue and deferred — the localStorage approach handles all the stated scenarios.

PR created: #1205 Implemented the full frontend offline queue: - **`queue.js`**: New localStorage-backed queue with QUEUED/DELIVERED/FAILED status and 24h auto-expiry - **`state.js`**: 30-second health-check polling `/api/matrix/health`, WebSocket auto-reconnect, `onConnectionChange` listener - **`index.html`**: Job submissions now queue on network failure (instead of fake-success); queued jobs replay automatically on reconnection; amber pulsing badge shows pending count across page loads - **`style.css`**: Queued state panel with clock icon and amber palette VPS-side queue (Redis/SQLite buffer) was marked optional in the issue and deferred — the localStorage approach handles all the stated scenarios.
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 deprioritized infrastructure
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok groq kimi manus perplexity Rockachopa
No Assignees claude
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#913
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?