I burned $250 in tokens on day one with OpenClaw. Here's why.

Published: (March 19, 2026 at 09:25 PM EDT)
2 min read
Source: Dev.to

Source: Dev.to

Overview

Cover image for I burned $250 in tokens on day one with OpenClaw. Here's why.

No production traffic. No customers. Just me testing a few simple workflows.

The culprit wasn’t one big request. It was four things compounding:

  • Context creep. I kept adding “just one more thing” to prompts—prior decisions, more context, and more detail. Each run got bigger without feeling bigger.
  • Tool output bloat. Logs, diffs, API responses flowing straight into the next step. Output becomes input becomes output. It adds up fast.
  • Scheduled job overhead. Cron jobs re‑establishing a large prompt footprint on every run. Not catastrophic — just quietly expensive, repeatedly.
  • Duplicate triggers. A couple of retries running the same bloated job twice.

The fix was kinda boring: smaller context windows, trim tool outputs aggressively, fresh session boundaries on scheduled jobs, and, most importantly, stop using the most expensive model by default for everything. That last one alone cut most of the cost.

After a while I got bored of switching models and decided to turn this into a research opportunity. I published RoBC on GitHub and then trained it and put it into production on clawpane.co.

Let me know if you check the repo out or if you need help with your AI spending.

0 views
Back to Blog

Related posts

Read more »

You're not prompting it wrong.

Background I was listening to Grady Booch on The Third Golden Age of Software Engineering episode of The Pragmatic Engineer. During the episode he mentioned a...

AI Vocab 101

Why Vocabulary Matters When Talking About AI I've been having a lot of conversations with non‑tech people recently about AI. What I keep running into is the sa...