OpenClaw Token Optimizer

Overview

Deliver a practical audit and configuration plan that cuts input tokens and unnecessary calls while keeping answer quality. Provide concrete config edits, workspace file trimming guidance, and a prioritized rollout plan.

Workflow

1) Scope and locate configuration

• Identify the OpenClaw config file location (common paths include ~/.openclaw/openclaw.json, .openclaw/openclaw.json, or project root config).
• List injected workspace files in scope (e.g., AGENTS.md, SOUL.md, TOOLS.md, IDENTITY.md, USER.md, HEARTBEAT.md, MEMORY.md, and memory/YYYY-MM-DD.md).
• Confirm provider and model support for prompt caching and memory search to avoid proposing unsupported keys.

2) Baseline token sources

• Break input cost into buckets: system prompt, tool schema, workspace files, memory files, and conversation history.
• Use a rough sizing method if exact token counts are unavailable (e.g., characters/4 as a quick estimate) and call out that the estimate is approximate.

3) Input reduction (highest ROI)

• Trim workspace files first. Target budgets:
  • AGENTS.md: keep only essential agent rules and policies.