Cron sessions and context management
I am running OpenClaw local on MacOS. I am eating up rate limits at a disproportionate pace.
This started happening after I recently set up 3 cron jobs to 1) check for updates 1x per day 2) take a backup, apply updates, test, rollback if needed. 1x per day 3) self-repair Discord connections every 15 mins
I found there were many active sessions for these jobs today after letting the system run on its own for a few days.
And that my usage had been consumed, which seems like an issue with context management.
Questions:
A) does every cron job spin up a unique session by default, e.g., does each cron run trigger a full system prompt?
B) is it more efficient to run these kinds of crons as “Isolated” or “Main”?
C) does pruning help free up context, or can pruning have the reverse effect of driving up usage?
This started happening after I recently set up 3 cron jobs to 1) check for updates 1x per day 2) take a backup, apply updates, test, rollback if needed. 1x per day 3) self-repair Discord connections every 15 mins
I found there were many active sessions for these jobs today after letting the system run on its own for a few days.
And that my usage had been consumed, which seems like an issue with context management.
Questions:
A) does every cron job spin up a unique session by default, e.g., does each cron run trigger a full system prompt?
B) is it more efficient to run these kinds of crons as “Isolated” or “Main”?
C) does pruning help free up context, or can pruning have the reverse effect of driving up usage?
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
134,827Members
Resources
Similar Threads
Was this page helpful?
