By job, not by team
The right CLI is the one that fits the job — not the one your friend uses or the one with the loudest blog post. A simple framework: (1) what's the workload (code editing? research synthesis? remote tasks? web automation?), (2) what's the trust profile (your repo or someone else's? sensitive code or experimental?), (3) what's the cost shape (one-off, recurring, parallel fan-out?).
Practical defaults: code editing in your terminal → Claude Code (deepest IDE-like flow), Codex (open-source, multi-provider auth), or Gemini (1M context, free tier). Knowledge work, file-native research → Cowork. Mobile-to-Mac async → Dispatch. Long sessions across machines → Claude Remote. Web tasks, booking/forms → Operator. Quick async questions → Claude.ai or ChatGPT Desktop.