This is the way
Mine is a simple cli that lets its make a well defined task with own worktree and session in filesystem
Manager session can inspect any directly request changes - steer etc
This has fundamentally changed how I use Codex
- everything runs out of a single persistent thread (my "chief of staff")
- anytime I start a new project or workstream, I have that thread spin up a new thread (because it's already found the context from slack, etc)
- the CoS thread checks in on the project threads during heartbeats, and occasionally sends relevant updates from slack to that thread
everything flows naturally to the top