Skip to content

docs: document dashboard WebSocket troubleshooting #426

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
douglasmonsky wants to merge 1 commit into
base: codex/symphony-pilot
Choose a base branch
from
Open

docs: document dashboard WebSocket troubleshooting #426

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 22 additions & 0 deletions docs/symphony/operations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -101,6 +101,28 @@ GitHub metadata. It does not scrape terminal logs.
The local branch and the expected `codex/symphony-gh-<number>` delivery branch
are reported separately so a missing publication is visible.

### Troubleshoot an Offline LiveView Badge

If a headless dashboard capture shows an offline badge, first check the service:

```bash
scripts/status-symphony
```

Then check the JSON API directly:

```bash
curl --fail http://127.0.0.1:4000/api/v1/state
```

If both checks succeed, Symphony and its API are healthy. The offline badge
describes the browser's LiveView WebSocket state, which a headless capture may
fail to maintain; the badge alone is not evidence that the service is down. It
can still indicate a real WebSocket problem. Inspect
`~/.codex/symphony/agent-maintainer/service.log` for errors and open
`http://127.0.0.1:4000/` in a normal interactive browser to confirm whether the
LiveView connection remains online.

## Intervene from Desktop

1. Remove `agent-ready` to prevent a new claim.
Expand Down