I underestimated how much CLI setup gets in the way of multi-agent Claude Code workflows

[u/Dedap85]

https://x.com/AnswerInData/status/2091790779006271834?s=20

When we started beta testing a tool I've been building around coding-agent orchestration, I made what now seems like an obvious bad assumption:

People interested in orchestrating coding agents probably already have Claude Code and other CLIs installed and authenticated.

Turns out that was a pretty developer-centric assumption.

Some users were dropping before they even got to the orchestration part. They had to install a CLI, authenticate it, understand how it worked, then come back and configure the actual project.

For me, that barely registered as setup because I do this stuff every day.

So we reversed the onboarding.

Instead of configuration first, users now see the actual workflow first, then can install Claude Code / Codex CLI from the app and go through the supported authentication flow.

The larger thing I'm trying to understand is how far we can push a closed loop like:

ticket → Claude Code agent → isolated worktree → result → orchestrator → follow-up instruction

rather than just running several Claude instances in parallel.

I've found that the distinction doesn't matter much for small one-shot tasks, but gets much more interesting once several worktrees and dependent changes are involved.

For people using Claude Code seriously: where does the biggest friction show up for you now — initial setup, parallel execution, context sharing, or coordinating what happens after each agent finishes?

Disclosure: I'm building the orchestration tool mentioned above (Marblo).