Blog

February 4, 2026

Managing My AI Team From a Dashboard

How Codex Desktop changed the way I think about AI-augmented development.

Managing My AI Team From a Dashboard

Why I Cared About This At All

I initially dismissed GUIs for coding agents. The CLI is fast, flexible and I know my way around it. Why would I want a window?

Then OpenAI shipped Codex Desktop. And it changed everything.

The breakthrough wasn’t the model itself. It was the ability to see all agents across all projects simultaneously. StarDust threads here. Aligno there. Client work below. All running, all visible, all interruptible.

Unlike Cursor (which gives you one window per project), Codex Desktop displays everything at once. Fire off tasks, switch contexts, come back when input is needed. I feel less like a developer now and more like a manager of a small engineering team that happens to be AI.

The Claude vs Codex Reality

Claude Code remains my daily driver. It’s fast, efficient and excellent at problem-solving. When I need something done right now, Claude is where I go.

Codex feels slower at first. But it demonstrates a superior ability to ask the right questions before diving in. The subtle details that Claude misses, and I’d have to catch manually? Codex just asks about them upfront.

The tradeoff is real: Claude occasionally introduces bugs that slip through because of its speed. Codex prioritizes thoroughness over velocity. But I’m not switching. I’m expanding headcount.

YOLO Mode

Codex has a mode that grants full permissions without approval prompts. Potentially dangerous. Absolutely liberating.

I enabled it immediately. The risk is worth the uninterrupted flow, and I rely on git and backups for safety. If you’re comfortable with version control, YOLO mode turns Codex into something genuinely autonomous.

Meanwhile, Claude Isn’t Standing Still

Recent developments from Anthropic:

  • Sonnet 5: Expected imminently with 1 million token context, half the price of Opus and strong coding benchmarks
  • Xcode 26.3: Now supports both Claude Agent SDK and Codex natively with model-agnostic MCP support
  • Claude Code v2.1.30/v2.1.31: Performance improvements that finally stopped my MacBook from overheating
  • Native multi-agent orchestration coming to Claude Code

Where I’m Landing

My current strategy: Claude for deep, focused work. Codex for parallel cross-project management.

If Sonnet 5 delivers on its promises and Claude Code ships proper multi-agent support, I’ll likely consolidate back to one ecosystem. But right now, the combination is more powerful than either tool alone.

The competitive pressure between these platforms is accelerating improvements on both sides. As a user, that’s exactly what I want to see.

Have something in mind?
Get in touch.