Slash Agent Start-Up Tokens by 60%: Clean Up Your Bot's Workspace

A developer on r/openclaw shared a practical method to drastically reduce start-up token consumption for LLM-based coding agents. The approach: run an LLM over all markdown files in the workspace root to identify and eliminate bloat and duplication.

Key Actions

• Reviewed every markdown file at the workspace root for redundant or overly verbose content (e.g., change logs, duplicated memories, user info).
• Structured the remaining files similarly to a memory system for consistency.
• Used a CLI tool (codex) instead of going through the agent to keep the process objective.
• Created a TOOLS file with quick notes and a separate tools/ folder with per-tool details that the agent can pull on demand.
• Added new files like voice to maintain a consistent tone across different models.

Results

Start-up tokens dropped from 80k to 31k—a 61% reduction. The workspace became leaner and the agent more responsive without losing essential context.

Why This Matters

High start-up tokens translate to slower response times and higher costs. Regularly auditing workspace files with an LLM—outside the agent loop—prevents bloat accumulation and keeps token budgets under control.

Who This Is For

Developers running long-lived AI coding agents who want to cut token waste and improve agent performance without sacrificing context quality.