How CodeCondense works
A transparent layer between Claude and its tools. Zero config. Zero workflow change.
The optimization loop
Plugin intercepts tool calls
When Claude Code makes a tool call (Read, Search, Edit, etc.), CodeCondense intercepts it before it reaches the native handler.
Smart routing decision
CodeCondense checks its AST index, session memory, and delta cache to decide the most efficient way to fulfill the request.
Optimized response returned
The optimized result — often combining what would have been 5–8 separate calls — is returned to Claude in the same format it expects.
Before vs after — by tool
grep -r "useAuth" . (6,200 tokens)
Read auth/hooks.ts (8,100 tokens)
Read auth/context.tsx (7,400 tokens)
grep -r "useAuth" src/ (5,900 tokens)
Read shared/hooks.ts (4,200 tokens)
— Total: 5 calls, 31,800 tokens, $0.159
Search({ query: "useAuth", output_mode: "file_paths_with_content" })
— Returns: matches + file content + AST symbols
— Total: 1 call, 4,100 tokens, $0.021
— Saved: $0.138 (87%)