As far as I understand, this is precisely how the Orchestrator in Kilo Code structures the execution of a task (or project). It familiarizes itself with the OVERALL task, breaks it down into smaller fragments, and then, one by one, uses message commands to assign these parts to the Assistants – such as the Architect, Coder, Debugger, and so on. It seems to me that the same algorithm is being used, isn't it?
Unfortunately, the `/newtask` switch didn't seem to work. It still sends out the same context size and still hit the context size limit error with anthropic. My context has grown 80k in just few prompts. I discovered that kilo included irrelevant files to my prompt.
As far as I understand, this is precisely how the Orchestrator in Kilo Code structures the execution of a task (or project). It familiarizes itself with the OVERALL task, breaks it down into smaller fragments, and then, one by one, uses message commands to assign these parts to the Assistants – such as the Architect, Coder, Debugger, and so on. It seems to me that the same algorithm is being used, isn't it?
Yes, that's right. Orchestrator does create smaller subtasks and they don't share context window (each task has it's own).
Unfortunately, the `/newtask` switch didn't seem to work. It still sends out the same context size and still hit the context size limit error with anthropic. My context has grown 80k in just few prompts. I discovered that kilo included irrelevant files to my prompt.
I've noticed the same issue with the /newtask https://github.com/Kilo-Org/kilocode/issues/424