4 ms·
The problem is that every time you run your full automation with linting and tests, you’re filling up the context window more and more. I don’t know how people
by yahoozoo 1y ago
The problem is that every time you run your full automation with linting and tests, you’re filling up the context window more and more. I don’t know how people using Claude do it with its <300k context window. I get the “your message will exceed the length of this chat” message so many times.
- diggan 1y agoI don't know exactly how Claude works, but the way I work around this with my own stuff is prompting it to not display full outputs ever, and instead temporary redirect the output somewhere then grep from the log-file what it's looking for. So a test run outputting 10K lines of test output and one failure is easily found without polluting the context with 10K lines.
- the_mitsuhiko 1y agoI started to use sub agents for that. That does not pollute the context as much
- abdullin 1y agoClaude's approach is currently a bit dated. Cursor.sh agents or especially OpenAI Codex illustrate that a tool doesn't need to keep on stuffing context window with irrelevant information in order to make progress on a task. And if really needed, engineers report that Gemini Pro 2.5 keeps on working fine within 200k-500k token context. Above that - it is better to reset the context.