OpenClaw users report high API costs from vague prompts, developer advises structured workflows

A Reddit discussion highlights a common issue with AI coding agents like OpenClaw: users treating them as wish-granting genies rather than structured orchestration tools. The post describes a $300 Anthropic bill resulting from vague prompting without clear workflow or constraints.

The problem: Vague goals burn tokens

According to the source, when users provide "a vague goal, no workflow, no structure, no clear state.. no constraints," the system "wanders and burns tokens like a crackhead at a copper convention." This happens because the underlying system has "zero direction aside from unrealistic expectations."

The solution: Build intentions first

The community advice is clear: "OpenClaw works best when you build your intentions first, then tell it to scan the repo and do the minimum work necessary." The orchestrator should operate on "put-together pieces, not trying to hallucinate the entire machine from your wishful thinking."

The source emphasizes that OpenClaw is "a conductor, not a miracle worker" and notes frustration from users expecting it to "magically become architect, builder, debugger, and mind reader." While you "might get lucky now and then," treating it this way means "you're basically just gambling with api credits."

Current limitations

The discussion acknowledges that while the technology might advance in "maybe 5 years," right now "we are just not there yet." The practical approach is to provide clear structure and realistic expectations rather than hoping for magical solutions.