What problem does it solve?
This guide collects diagnostic checks and actionable fixes for GasTown operational problems reported by the GT doctor and agent terminals, including doctor check failures, tmux terminal anomalies, service startup problems, and beads/address inconsistencies.
Core Features & Use Cases
- Doctor diagnostics: Interpret common doctor failures such as agent-beads-exist, patrol-not-stuck, clone-divergence, and priming limits and apply prescribed remediation steps.
- Terminal recovery: Restore orphaned tmux input, clear popup overlays, and reinitialize missing sessions to recover agent terminals.
- Service operations: Verify daemon and mayor status, reinitialize dashboards, run gt doctor fixes, and nudge mayor processes when unresponsive.
- Beads and address guidance: Explain message ID prefixes, address storage differences, and flexible query approaches for bead lookups.
- Escalation criteria: Provide thresholds and documentation steps for when to escalate persistent failures or potential data loss.
Quick Start
Run the troubleshooting checklist to diagnose a failing gt doctor report, recover tmux terminals, restart or nudge services, and escalate if issues persist.