如何在 Codex 中用好 coordinator 聊天？我始终调不好

After a miserable experience trying to use my 'dot' as a coordinator for multiple Codex chats (more on that in a moment), I am back to what I have been doing since Astra arrived and not happy with it so looking to see how you all are managing this problem.

Shortest version: I use one "Coordinator" chat per project I am working on, one "Build" and then I usually have 3-8 others for very specific areas to work on within the projects (think major features).

The Coordinator monitors the progress (timed) of the other chats and they also report to it as needed (finished, blocked, etc). This more or less works ok until you start dealing with context windows.

Once it gets to compacting regularly it's time for a refresh handoff. Coordinating when this gets done for each chat is a pain and on the occasions I can actually do a refresh on all the chats including the Coordinator at the same time, the turnaround time until everything is up and running again is frustrating.

Also I discovered chats like the Coordinator cannot Resume or edit other chat's Goals so I have to manage that by hand as well.

As for 'dot'. Apparently because it also operates on its own 'computer' in the cloud, it turns out it unknowingly sucks at trying to coordinate or manage local chats. I feel like this is going back in time, clearly released too soon, and wildly confident in its abilities but also very wrong about that.

Listening to the phone ringing when I 'call' the dot, is a really odd experience in this setting as well.

SO YEAH - not withstanding the suckiness of dot, how are you managing the coordination of on-going efforts E.G. Goals as well as context windows in Codex?

Cheers