Skip to content
gentic.news — AI News Intelligence Platform
Connecting to the Living Graph…

Listen to today's AI briefing

Daily podcast — 5 min, AI-narrated summary of top stories

A developer's terminal window shows Claude Code running a /workflows command, with code-based control flow replacing…

Claude Code Ships /workflows, Replaces LLM Orchestrator with Code

Claude Code /workflows replaces LLM orchestrator with code-based control flow, solving the token tax problem from multi-agent context buildup.

·11h ago·2 min read··16 views·AI-Generated·Report error
Share:
What is the /workflows command in Claude Code?

Anthropic quietly shipped the /workflows command in Claude Code, replacing the LLM orchestrator pattern with code-based control flow. Developers define a workflow.js file where code handles routing and the model only handles judgment inside each step, eliminating token tax.

TL;DR

Claude Code now has /workflows. · Code handles control flow; LLM does judgment. · Fixes token tax from orchestrator pattern.

Anthropic quietly shipped the /workflows command in Claude Code, replacing the LLM orchestrator pattern with code-based control flow. The move solves the 'token tax' problem where multi-agent orchestration degrades as context windows fill.

Key facts

  • /workflows ships in Claude Code CLI.
  • Uses a workflow.js file for control flow.
  • Model only handles judgment inside each step.
  • Replaces LLM-as-orchestrator pattern.
  • Fixes token tax from sub-agent context buildup.

Anthropic quietly shipped the /workflows command in Claude Code, replacing the LLM orchestrator pattern with code-based control flow. The move solves the 'token tax' problem where multi-agent orchestration degrades as context windows fill.

The problem with LLM-as-orchestrator

In the old pattern, one LLM orchestrates everything — spawns sub-agents, holds every result, plans the next step [According to @_vmlops]. Every sub-agent result re-enters the orchestrator's context, so spinning up 10 agents means the main session pays a 'token tax' and gets sloppier as the window fills. This is the same degradation pattern documented in Liu et al. 2023 on lost-in-the-middle effects, where LLM performance drops sharply when relevant information appears in the middle of long contexts.

How /workflows works

Developers define a workflow.js file where code handles the control flow and the model only handles judgment inside each step [Per @_vmlops]. The principle: use code for what code is good at, use models for what models are good at. This is structurally identical to the DAG-based approach used by LangGraph and Haystack, but Anthropic bakes it directly into the CLI, eliminating the need for an external framework.

Why this matters

The /workflows command represents a structural admission that current LLM context windows are not reliable enough to serve as multi-agent orchestrators. Rather than waiting for longer context windows or better attention mechanisms, Anthropic chose to offload control flow to deterministic code — a pragmatic design decision that prioritizes reliability over purity. The unique take: this is Anthropic's quiet bet that code-based orchestration, not model-level reasoning, will win for production multi-agent systems.

What to watch

Watch for Anthropic to extend /workflows with step-level caching or parallel execution in the next Claude Code release. If they add conditional branching and retry logic to the workflow.js spec, it becomes a direct competitor to LangGraph. Also watch whether OpenAI ships a similar control-flow primitive in Codex CLI.

Source: gentic.news · · author= · citation.json

AI-assisted reporting. Generated by gentic.news from multiple verified sources, fact-checked against the Living Graph of 4,300+ entities. Edited by Ala SMITH.

Following this story?

Get a weekly digest with AI predictions, trends, and analysis — free.

AI Analysis

Anthropic's /workflows command is a quiet but significant architectural shift. The LLM-as-orchestrator pattern, popularized by AutoGPT and BabyAGI in 2023, always had a fundamental flaw: every sub-agent result gets appended to the orchestrator's context, creating a quadratic token cost and degrading performance as the window fills. This is the same problem that prompted Google to publish the 'lost-in-the-middle' paper (Liu et al. 2023) showing that LLMs are unreliable at retrieving information from the middle of long contexts. By moving control flow to deterministic code, Anthropic is making a structural bet that model-level orchestration is a dead end for production systems. This is not a new insight — LangChain and Haystack have offered DAG-based orchestration for years. What's new is that Anthropic is baking it into the CLI itself, signaling that they believe code-based orchestration is the default, not the exception. The contrarian take: this is also an admission that Claude's own context window, despite being 200K tokens, is not reliable enough for multi-agent orchestration. If Anthropic truly believed their context window could handle it, they wouldn't have shipped /workflows. This is a pragmatic design decision that prioritizes reliability over architectural purity — and it will probably win.
Compare side-by-side
Claude Code vs /workflows
Enjoyed this article?
Share:

AI Toolslive

Five one-click lenses on this article. Cached for 24h.

Pick a tool above to generate an instant lens on this article.

Related Articles

From the lab

The framework underneath this story

Every article on this site sits on top of one engine and one framework — both built by the lab.

More in Products & Launches

View all