I'm wondering if in large projects, you want subagents to avoid having tasks flush out the main context?

If you're working with large source files, you might want to do each piece of work in an independent context with the information discarded afterwards?

Is the context a sliding window, or are there tiers of importance?

▲

faangguyindia 3 days ago | parent [-]

No the context going out of control is overblow. Lemme example why. First you need to work at feature level. It shouldn't be too large of a feature in one go.

Let's say in my workflow, first agent must know where it needs to make changes? So it greps bunch of files and reads them. We do not need these read calls or grep calls to be part of history, the knowledge gained by doing these is what needs to be part of context

Finally, we do some risk analysis and then just code it right away.

No sliding window needed for this

After this you reset context /reset and u start on new feature.

	▲	ejstronge 3 days ago \| parent [-]
		> No the context going out of control is overblow. Lemme example why. First you need to work at feature level. It shouldn't be too large of a feature in one go. As a meta point, why write ' Lemme example why.' ? If someone is still with you at this sentence, that person was ready to understand why. Otherwise, it delays (and thus endangers the visibility of) whatever your explanation was going to be.