A 4,000-line stack trace or verbose build log is mostly repetition the model doesn't need. Extract the signal first; pasting the whole thing is the single most wasteful coding-assistant habit.
Pipe Logs Through head/grep Before Pasting Them Into an Assistant
🔒 Pro tip · Advanced
Unlock this tip — and 119 more
This is one of 120 advanced, fact-checked tactics reserved for Pro. Get the full 142-tip library, a searchable archive, and a new tip every morning. Free for 7 days, then $9/mo.
Prefer to browse? The 22 Beginner tips are free forever.
More in Coding Assistants
💻Coding Assistants
Often cuts output tokens 40-70% on edits to large files, varies by file size
Ask for the Patch, Not the Whole File
When editing an existing file, tell the assistant to return only the changed lines as a diff or snippet instead of regenerating the entire file.
💻Coding Assistants
often 30-60% on long sessions
Run /clear Between Tasks in Claude Code Instead of Letting Context Pile Up
Claude Code resends the whole conversation every turn. Finishing one task and starting an unrelated one in the same thread means you keep paying for stale tool output and dead files.
💻Coding Assistants
10-30% on context-heavy chats
Add a .cursorignore So Cursor Stops Indexing Your node_modules
Cursor's @codebase and automatic context can pull in build artifacts, lockfiles, and vendored dependencies. A .cursorignore file keeps that noise out of every prompt.