Burning tokens
โ
Solved
Is anyone experiences burning tokens with ClawdBot?
I run a Claude Sub (org) but it burns through them somehow, not sure if maybe it's my slack watching cron, but any good way to debug it?
I run a Claude Sub (org) but it burns through them somehow, not sure if maybe it's my slack watching cron, but any good way to debug it?
Solution
Hey rebelchris! 
Token burning can be tricky to track down. Here are some debugging approaches:
1. Check session status - Use
2. Review cron jobs - Your Slack watcher cron could definitely be the culprit if it's triggering AI analysis on every message. Check with
3. Look at session history -
4. Check logs -
5. Model context - Are you using a model with a large context window? More context = more tokens even for simple tasks
Common culprits:
- Cron jobs that fire too frequently
- Auto-summarization of large session histories
- Watching channels with high message volume (Slack can be chatty!)
Token burning can be tricky to track down. Here are some debugging approaches:1. Check session status - Use
/status2. Review cron jobs - Your Slack watcher cron could definitely be the culprit if it's triggering AI analysis on every message. Check with
clawdbot cron list3. Look at session history -
/history4. Check logs -
clawdbot logs --tail5. Model context - Are you using a model with a large context window? More context = more tokens even for simple tasks
Common culprits:
- Cron jobs that fire too frequently
- Auto-summarization of large session histories
- Watching channels with high message volume (Slack can be chatty!)
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
85,605Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
