Quick diagnosis and repair for Discord bot, Gateway, OAuth token, and legacy config issues. Checks connectivity, token expiration, and cleans up old Clawdis artifacts.
Real data. Real impact.
Growing
Developers
Per week
Open source
Skills give you superpowers. Install in 30 seconds.
Quick diagnosis and repair for Discord/Gateway availability issues, OAuth token problems, and legacy Clawdis configuration conflicts.
# Check status (diagnostic only) discord-doctorCheck and auto-fix issues
discord-doctor --fix
clawdbot healthWhen run with
--fixcom.clawdis.gateway.plist~/.clawdis~/.clawdis-backup| Issue | Auto-Fix Action |
|---|---|
| Gateway not running | Starts gateway on port 18789 |
| Missing npm packages | Runs |
| Discord disconnected | Restarts gateway to reconnect |
| OAuth token expired | Shows instructions to re-authenticate |
| Legacy launchd service | Removes old |
| Legacy ~/.clawdis config | Moves to |
If you see "Access token EXPIRED", run:
cd ~/Clawdis && npx clawdbot configure
Then select "Anthropic OAuth (Claude Pro/Max)" to re-authenticate.
If you upgraded from Clawdis to Clawdbot, you may have legacy artifacts causing OAuth token conflicts:
~/Library/LaunchAgents/com.clawdis.gateway.plist~/.clawdis/Run
discord-doctor --fixDiscord Doctor Checking Discord and Gateway health...
Discord App Running (6 processes)
Gateway Process Running (PID: 66156, uptime: 07:45)
Gateway HTTP Responding on port 18789
Discord Connection Discord: ok (@Clawdis) (321ms)
Anthropic OAuth Valid (expires in 0h 45m)
Legacy Clawdis No legacy launchd service No legacy config directory
Recent Discord Activity
- discord:group:123456789012345678 (21h ago)
Summary All checks passed! Discord is healthy.
No automatic installation available. Please visit the source repository for installation instructions.
View Installation Instructions
1,500+ AI skills, agents & workflows. Install in 30 seconds. Part of the Torly.ai family.
© 2026 Torly.ai. All rights reserved.