Claude and Codex can also use the cook command to coordinate runs of other agents. This is similar to how you can describe a workflow to them of how to use subagents, and they'll try, but this gives them a reliable deterministic way to run those agents. An added benefit of having Claude/Codex/etc. use cook directly is that they are really good at analyzing the traces of what is happening inside of cook and after the fact.
Very nice. However, I do like to read every agent summary before letting them move on. I'm not sure I'd be able to apply this level of automation to many tasks.
But that's one of the first things you fix in your CLAUDE.md:
- "Only do what is asked."
- "Understand when being asked for information versus being asked to execute a task."
How do you do that???? Say the words but in the form of a question? I feel like that will go a lot worse than just telling (but nicely). I have a daughter too so I am genuinely willing to try anything
They are releasing auto-mode soon. But that won't improve the underlying permission system, rather, it'll just delegate decisions to Claude. That's better than --dangerously-skip-permissions, but not great for those that want granular controls and are sensitive to the extra tokens spent.
Sure but I don't find them irreplaceable. Actually anthropic models have dropped out of my top ten usage this month. I only use opus occasionally for writing plans, its been pretty unreliable at executing.
The US is such a shit show. Personally I hope this doesn't affect Anthropic's growth and development because I quite enjoy using their products and see them evolve.
reply