| ▲ | theptip 2 days ago | |
> Finally it occurred to me to put context where it was needed - directly in the test files. Probably CLAUDE.md is a better place? > Too much context Claude’s Sub-agents[1] seems to be a promising way of getting around this, though I haven’t had time to play with the feature too much. Eg when you need to take a context-busting action like debugging dependencies, instead spin up a new agent to read the output and summarize. Then your top-level context doesn’t get polluted. [1]: https://docs.anthropic.com/en/docs/claude-code/sub-agents | ||
| ▲ | nicwolff 2 days ago | parent | next [-] | |
I've added a subagent to read the "memory_bank" files for project context after being told the task at hand, and summarize only the pertinent parts for the main agent. This is working well to keep the context focused. https://gist.github.com/nicwolff/273d67eb1362a2b1af42e822f6c... | ||
| ▲ | swader999 2 days ago | parent | prev [-] | |
I wrote three sub agents this week, one to run unit tests, another to run playwright and a third to write playwright. These are pretty basic boundaries that aren't hard to share context between agent and the orchestrating main agent. It seemed to help a lot. I also have complex ways to run tests (docker, data seeding, auth) and previously it was getting lost. Only compacted a couple times. Was a big improvement. | ||