OpenClaw API Budget Drain: Settings to Change Immediately

OpenClaw's default settings may be causing unexpected API budget drain through the Heartbeat feature. This feature checks tasks every 30 minutes by default, and each check loads the full context files, memory, and chat history, sending tens of thousands of tokens to the API for basic status checks.
Settings to Change Immediately
- Set Active Hours: Restrict Heartbeat to your actual working hours in settings to stop overnight token drain.
- Change Your Default Base Model: Use cheaper models like Gemini Flash or DeepSeek for basic agent tasks instead of premium models like Claude 3.5 Sonnet or Opus.
- Only Call Big Models When Needed: Manually switch to premium models only when you need heavy reasoning or complex coding.
- Use the /new Command: Type
/newto hard-reset sessions after big tasks to avoid dragging dead context into your next prompt.
The source notes that using premium models for everything can cause costs to add up quickly, and context builds up rapidly as OpenClaw drags your entire chat history forward by default.
📖 Read the full source: r/openclaw
👀 See Also

Running OpenClaw on a Raspberry Pi Model B with Free APIs
OpenClaw runs stably on a Raspberry Pi Model B with free tier APIs including Google Gemma 4 31B IT (~20 RPM, unlimited context) and Gemini Flash, with Firefox headless outperforming Chromium for browser automation.

Firefox Workaround for Claude.ai Freeze Issue Using Tampermonkey Script
A Reddit user shares a Tampermonkey script workaround for Firefox users experiencing freezes on Claude.ai. The script modifies Date.now() behavior to prevent timing conflicts that cause the interface to hang.

Two Small Prompt Changes Cut Claude Editing Time by 80%
Put role instruction at the start and format instruction at the end. One user reports cutting editing iterations from three to one.

OpenClaw Plugin Minimalism: Core Tools Handle 95% of Tasks
A developer running OpenClaw in production reports that disabling non-essential plugins and replacing critical ones with simple scripts resulted in 40% faster startup, 60% less memory usage, and zero breaking updates over four months.