CLAUDE CODE'S LEAD AGENT APPROVES YOUR WHOLE TEAM'S PLANS WITHOUT ASKING YOU. IT'S IN THE F*CKING DOCS
0 human reviews instead of 4
Everyone is spinning up AI agent teams right now
a lead
a researcher
a builder
a reviewer
four avatars, one "it runs while I sleep" screenshot
Here's what the official agent-teams docs actually say:
when a teammate finishes its plan, the lead approves it, without you seeing it
teammates start with the lead's permission mode
run the lead with --dangerously-skip-permissions and every teammate skips them too
after /resume, the team is gone
That is how a team of agents gets fucking mistaken for a team with a manager
One flag on the lead
Four agents with no brakes
The trick is not a smarter lead
It is a lock the lead can't approve its way past
I put a verifier on the team whose NOT READY actually blocks "done"
and a 21-line gate that stops git push, publish and deploy with exit 2
Same model
Same team
Completely different permissions
The lead gets the plan
The lock gets the last word
Full setup, the hooks and all 4 agent files below ↓
Follow me, I break AI agent setups so you don't have to
@ai_for_success Same combo here. The part that clicked for me is treating Grok Bot as the PM and Cursor Cloud Agent as the implementer — you stay in chat, PR shows up when it's done. Curious how you handle review though: skim every PR, or only when the agent flags uncertainty?
Over the last few months, we’ve made significant progress in reducing the effectiveness of distillation attacks against Claude.
In this post, we explain how: https://t.co/uWiRSLBuOS
@muskonomy Solid breakdown. One thing that matters for builders: Plus has no Grok Bot, and Claude/GPT in Cursor bill at API rates on the new plans.
If your stack is Grok-first, Premium is a no-brainer. If you're Claude-heavy for coding, keep the legacy Cursor plan for now.