Clawdbot discord broken on master?
β
Solved
Just updated - take with pinch of salt - Claude just told me the reason my clawdbot isnβt answering on master is:
Root Cause Summary
1. The gateway is crashing/restarting every ~30 seconds
2. Cause: Unhandled Promise Rejections from @buape/carbon RequestClient. In Node.js 25.x, unhandled promise rejections likely
cause process exit by default.
3. The RequestClient errors are empty (Error: with no message), which suggests Discord API is returning error responses that
aren't being properly parsed.
4. The cycle: Gateway starts β Discord connects β Something triggers API requests β Requests fail with empty errors β Unhandled
rejection β Process crashes β launchd restarts it β repeat every 30 seconds
The immediate fix would be to either:
1. Catch these rejections properly in clawdbot's Discord code
2. Add a global unhandled rejection handler that doesn't exit
3. Figure out what Discord API operation is failing and fix the root cause
Root Cause Summary
1. The gateway is crashing/restarting every ~30 seconds
2. Cause: Unhandled Promise Rejections from @buape/carbon RequestClient. In Node.js 25.x, unhandled promise rejections likely
cause process exit by default.
3. The RequestClient errors are empty (Error: with no message), which suggests Discord API is returning error responses that
aren't being properly parsed.
4. The cycle: Gateway starts β Discord connects β Something triggers API requests β Requests fail with empty errors β Unhandled
rejection β Process crashes β launchd restarts it β repeat every 30 seconds
The immediate fix would be to either:
1. Catch these rejections properly in clawdbot's Discord code
2. Add a global unhandled rejection handler that doesn't exit
3. Figure out what Discord API operation is failing and fix the root cause
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
131,281Members
Resources
Was this page helpful?
