troubleshooting

Diagnose and triage GasTown operational failures from GT doctor and tmux terminals.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/justSteve/GasTownOperations --skill troubleshooting-juststeve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: troubleshooting
Source: https://github.com/justSteve/GasTownOperations/tree/main/.claude/skills/troubleshooting
Command: npx skills add https://github.com/justSteve/GasTownOperations --skill troubleshooting-juststeve

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about troubleshooting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose GasTown operational failures reported by the GT doctor?

To diagnose GasTown operational failures, run the troubleshooting checklist to interpret gt doctor reports, identify issues like agent-beads-exist or patrol-not-stuck, and apply prescribed remediation steps for recovery.

How do I recover orphaned tmux terminals during GasTown operations?

To recover orphaned tmux terminals, restore missing tmux input, clear popup overlays, and reinitialize sessions as the gtuser account to resolve terminal anomalies and recover agent terminals.

What permissions do I need to fix GasTown service startup errors?

Fixing GasTown service startup errors requires access to the GT CLI, active tmux sessions as the gtuser account, and sudo privileges to run recovery commands, edit rig files, and perform git pulls.

How do I resolve clone divergence in GasTown rigs?

To resolve clone divergence in GasTown rigs, edit the affected rig files and run git pulls to synchronize the repository state and clear the divergence reported by the gt doctor check.

When should I escalate persistent GasTown doctor check failures?

You should escalate persistent GasTown doctor check failures when issues exceed defined thresholds or indicate potential data loss, documenting the troubleshooting steps already taken for the escalation.

What is the best way to nudge unresponsive GasTown mayor processes?

The best way to nudge unresponsive GasTown mayor processes is to verify daemon and mayor status, reinitialize dashboards, run gt doctor fixes, and nudge the mayor processes directly if they remain unresponsive.