My Claude Code workflows ran for days. Headless workers finished in minutes.

Description and use

<p>I run four projects with Claude Code. For a while, my long multi-agent jobs went through Claude Code's Workflow tool, and they kept running for days. Some never finished.</p> <p>Part of it was effort. Every agent in a workflow runs at the effort level of the session that started it, and a workflow script has no documented per-agent effort setting. So I kept switching model and effort by hand, trying to make the big jobs move. That became a job of its own.</p> <h2> The setup that worked </h2> <p>I split the roles.</p> <ul> <li> <strong>One interactive Claude Code session is the orchestrator.

Problem

<p>I run four projects with Claude Code. For a while, my long multi-agent jobs went through Claude Code's Workflow tool, and they kept running for days. Some never finished.</p> <p>Part of it was effort. Every agent in a workflow runs at the effort level of the session that started it, and a workflow script has no documented per-agent effort setting. So I kept switching model and effort by hand, trying to make the big jobs move. That became a job of its own.</p> <h2> The setup that worked </h2> <p>I split the roles.</p> <ul> <li> <strong>One interactive Claude Code session is the orchestrator.

Outcome

<p>I run four projects with Claude Code. For a while, my long multi-agent jobs went through Claude Code's Workflow tool, and they kept running for days. Some never finished.</p> <p>Part of it was effort. Every agent in a workflow runs at the effort level of the session that started it, and a workflow script has no documented per-agent effort setting. So I kept switching model and effort by hand, trying to make the big jobs move. That became a job of its own.</p> <h2> The setup that worked </h2> <p>I split the roles.</p> <ul> <li> <strong>One interactive Claude Code session is the orchestrator.

Evidence

My Claude Code workflows ran for days. Headless workers finished in minutes.

Source