Optimize

Scan your sessions for waste patterns and get ready-to-paste fixes.

Usage

codeburn optimize                # last 30 days (default)
codeburn optimize -p today       # today only
codeburn optimize -p week        # last 7 days
codeburn optimize --provider claude

Or press o in the dashboard when a finding count appears. Press b to return.

What It Detects

Detector	What it catches
Junk reads	Reads into `node_modules`, `.git`, `dist`
Duplicate reads	Re-reads of the same file in a session
MCP coverage	MCP servers with many tools but low usage
Unused MCP	Configured but never invoked servers
Bloated CLAUDE.md	Oversized context files (with `@-import` expansion)
Low read:edit ratio	Editing without reading leads to retries
Cache bloat	High cache_creation_input_tokens
Ghost agents	Defined but never-invoked agents
Ghost skills	Defined but never-invoked skills
Ghost commands	Defined but never-invoked slash commands
Bash bloat	Shell output limit above recommended 15K chars
Low-worth sessions	Sessions with cost but no edits or delivery
Context bloat	Input:output ratio above 25:1
Session outliers	Sessions costing 2x+ the project average

Coaching Notes

Alongside the ranked findings, optimize surfaces up to three workflow coaching notes drawn from session history: a high rate of user corrections, an unusually long median time to first edit, and files repeatedly reworked across sessions.

Applying Fixes

Config-class findings (an environment variable, a shell config change, a mv to archive an unused item) can be applied directly instead of copy-pasted:

codeburn optimize --apply              # interactively apply config-class fixes
codeburn optimize --apply --yes        # apply every appliable fix without prompting
codeburn optimize --apply --dry-run    # print the plan without changing anything
codeburn optimize --apply --only id1,id2   # restrict to specific finding ids

Every applied fix is backed up and journaled. Review what was applied with codeburn act list, and roll any of it back with codeburn act undo.

Health Grade

Findings are ranked by urgency (impact weighted against observed waste) and rolled up into an A to F setup health grade. Repeat runs classify each finding as new, improving, or resolved against a 48-hour recent window.

Fix Actions

Each finding includes a ready-to-paste fix:

A CLAUDE.md line to add
An environment variable to set
A mv command to archive unused items
A shell config change

Models Compare