I find it to be quite cautious too. Beyond the access prompts, the model itself tends not to take as much initiative when using a local machine. It often hands tasks off to me when it needs a web browser, for which I say “you drive” and it will. It’ll ask me to confirm in writing to perform an action on a local machine - sometimes to auto classifier knocks it back because I didn’t use the exact words. An example for this recently was pushing a new release to an internal TestFlight group - took several attempts but it wouldn’t accept so I did it manually, which a local session has no complaints doing.
The threads (or sub agents) can speak to each other and organise each other, threads can spin up scheduled tasks to check on things later, and threads are organised by status so you can see when something needs you, is working, or is done.
I’m personally a massive fan of it and it’s my main driver. Now having the coordinator more in the mix is a welcomed add and helps with the workflow when running multiple projects. At some stage, would love to have projects be able to talk / handoff to each other and a single dashboard across all projects to see where threads are up to.
reply