openclaw - 💡(How to fix) Fix Feature request: cron payload kind=script for direct shell execution [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#73270Fetched 2026-04-29 06:21:40
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
Participants
RAW_BUFFERClick to expand / collapse

Problem

All cron jobs currently use kind=agentTurn which spins up a full LLM agent session (~30-38k tokens of system prompt + skill injection). For cron jobs that simply execute a Python/Bash script and return NO_REPLY, this wastes significant tokens.

Impact

288 runs/day of a 5-minute model-fallback check cron consumed ~$180/day (Anthropic standard pricing) purely in LLM wrapper overhead. We migrated this to launchd but still have 14 similar cron jobs.

Suggested Fix

Add --script <command> or kind=script to openclaw cron add/edit that directly executes a shell command without starting an LLM agent session. The cron system already tracks runs and delivery — just skip the LLM.

extent analysis

TL;DR

Modify the cron jobs to use a script execution mode instead of launching a full LLM agent session to reduce token waste.

Guidance

  • Identify the 14 remaining cron jobs that can be optimized and determine if they can be modified to use the proposed --script <command> or kind=script flag.
  • Verify that the cron system can track runs and delivery without requiring an LLM agent session.
  • Test the modified cron jobs to ensure they execute correctly and do not incur unnecessary token costs.
  • Consider migrating other similar cron jobs to launchd if the --script flag is not feasible.

Example

No code snippet is provided as the issue does not contain specific code examples.

Notes

The proposed solution assumes that the --script <command> or kind=script flag can be implemented without significant changes to the existing cron system.

Recommendation

Apply workaround: Modify the cron jobs to use the --script <command> or kind=script flag to reduce token waste, as this approach has already shown cost savings in the migrated model-fallback check cron job.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix Feature request: cron payload kind=script for direct shell execution [1 participants]