Debug

When a Symphony run stalls, retries endlessly, or fails mysteriously, this walks you through the correlation dance between Linear tickets and Codex sessions. You'll grep symphony.log for issue_identifier keys, extract session_ids, and trace the lifecycle from startup through completion or failure. The investigation flow is methodical: narrow by ticket, pull the timeline, classify whether it's a stall loop or turn failure or worker crash, then capture evidence with the right identifiers. The commands are straightforward rg oneliners, and the guidance on reading Codex session logs as a three-stage lifecycle (start, stream, terminal event) is actually clarifying. It assumes you know the Symphony runtime already but saves you from wandering through logs blind.

skills.sh installs: 551
GitHub stars: 82
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add odysseus0/symphony --skill debug --agent claude-code

Installs into .claude/skills of the current project.

Files

Debug

Goals

Find why a run is stuck, retrying, or failing.
Correlate Linear issue identity to a Codex session quickly.
Read the right logs in the right order to isolate root cause.

Log Sources

Primary runtime log: log/symphony.log
- Default comes from SymphonyElixir.LogFile (log/symphony.log).
- Includes orchestrator, agent runner, and Codex app-server lifecycle logs.
Rotated runtime logs: log/symphony.log*
- Check these when the relevant run is older.