It's very simple. I have told Claude that it's my chief of staff and that it must delegate all tasks to subagents. That as my COS it must show initiative and only come to me for vision/decision making. I have hooks further enforcing this. It works really well because I am usually working on like 12 things at once. Feels like playing simultaneous chess. The COS agent helps me context switch/orchestrate everything. Subagents have their own context window so the COS context does not get polluted/filled up with low level subtask details. COS can effectively prompt the subagents. My main session does grow and I compact it from time to time. But since all the WIP is already captured in external state, compaction of the main session does not degrade performance.
alt Hacker News
It's very simple. I have told Claude that it's my chief of staff and that it must delegate all tasks to subagents. That as my COS it must show initiative and only come to me for vision/decision making. I have hooks further enforcing this. It works really well because I am usually working on like 12 things at once. Feels like playing simultaneous chess. The COS agent helps me context switch/orchestrate everything. Subagents have their own context window so the COS context does not get polluted/filled up with low level subtask details. COS can effectively prompt the subagents. My main session does grow and I compact it from time to time. But since all the WIP is already captured in external state, compaction of the main session does not degrade performance.
I have used this same pattern in my own harness and it works well there too. https://github.com/computerex/z
I hooked an instance of my harness up to telegram and now I talk to it from everywhere it and dispatches work out to subagents.