Rockachopa/alexanderwhitestone.com
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[claude] fix: Workshop connection HUD with timeout and retry (#5) #10

Merged
claude merged 1 commits from claude/issue-5 into main 2026-03-22 22:55:41 +00:00
Conversation 0 Commits 1 Files Changed 2 +175 -12
claude commented 2026-03-22 22:55:15 +00:00
Collaborator
Copy Link

Fixes #5

Problem

The Workshop page at /world/ was stuck on INITIALIZING forever because main.js was never loaded (script tag commented out), no WebSocket connection logic existed, and there was no status indicator or error handling.

Changes

  • Connection status HUD added to world/index.html — shows connection state (CONNECTING/ONLINE/OFFLINE) with a pulsing dot indicator, plus agent count
  • WebSocket connection logic in main.js — connects to tower-hermes backend at /ws/tower with 5s timeout
  • Auto-retry — retries up to 3 times with 3s delay between attempts
  • Clear error state — shows "OFFLINE — backend unreachable" with a manual Retry button when all auto-retries are exhausted
  • Enabled main.js — uncommented the script tag so the module actually loads

Acceptance Criteria

  • ✅ When backend is running, Tower initializes and shows agents
  • ✅ When backend is NOT running, Tower shows clear error after timeout with retry button
  • ��� Connection status indicator reflects actual state accurately
Fixes #5 ## Problem The Workshop page at `/world/` was stuck on INITIALIZING forever because `main.js` was never loaded (script tag commented out), no WebSocket connection logic existed, and there was no status indicator or error handling. ## Changes - **Connection status HUD** added to `world/index.html` — shows connection state (CONNECTING/ONLINE/OFFLINE) with a pulsing dot indicator, plus agent count - **WebSocket connection logic** in `main.js` — connects to `tower-hermes` backend at `/ws/tower` with 5s timeout - **Auto-retry** — retries up to 3 times with 3s delay between attempts - **Clear error state** — shows "OFFLINE — backend unreachable" with a manual Retry button when all auto-retries are exhausted - **Enabled main.js** — uncommented the script tag so the module actually loads ## Acceptance Criteria - ✅ When backend is running, Tower initializes and shows agents - ✅ When backend is NOT running, Tower shows clear error after timeout with retry button - ��� Connection status indicator reflects actual state accurately
claude added 1 commit 2026-03-22 22:55:16 +00:00
fix: Workshop connection status HUD with timeout and retry d4bbe157c2 
Fixes #5

The Workshop page was stuck on INITIALIZING forever because:
- main.js was never loaded (script tag was commented out)
- No WebSocket connection logic existed
- No status indicator or error handling

Changes:
- Add connection status HUD to world/index.html showing
  connection state (CONNECTING/ONLINE/OFFLINE) and agent count
- Implement WebSocket connection to tower-hermes with 5s timeout
- Auto-retry up to 3 times with 3s delay between attempts
- Show "OFFLINE — backend unreachable" with manual retry button
  when all auto-retries are exhausted
- Enable main.js module script

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
claude merged commit 64d711e256 into main 2026-03-22 22:55:41 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claude gemini google manus Rockachopa
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/alexanderwhitestone.com#10
Delete Branch "claude/issue-5"

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?