Software Engineer Explains How to Conserve Claude Code Tokens
A software engineer at a company using Claude Enterprise assumed unlimited usage meant never worrying about limits, until a mid-month error cut off an active session. A Slack thread revealed several teammates had hit the identical wall, which led to a usage meter buried in Claude Desktop settings and Claude Code Usage Monitor, a CLI tool that estimates burn rate across a rolling five-hour window.
What followed became a practical toolkit comprised of rtk, Caveman, and CodeGraph. The tools help conserve Claude tokens regardless of which plan you're on, but habit changes matter, too. For example, the engineer defaulted to Sonnet over Opus, audited a bloated CLAUDE.md down to conditional references, and ran /clear between tasks. Applied together, they took the engineer's own usage chart from a mid-June spike to a steady, lower burn rate.