ultracode to initiate the feature, which allows the agent to write orchestration scripts and deploy subagents. While "workflow" remains valid in natural language, it no longer serves as the primary automated trigger.The shift follows feedback regarding accidental activations. Because "workflow" is a standard term, the agent occasionally launched agent orchestration—the coordination of multiple AI agents working together—when users intended a simple conversation. Moving to a unique keyword ensures that spinning up a subagent fleet is a deliberate user choice.
Users can trigger this by typing ultracode in the CLI. This mode is optimized for complex tasks where a single request spawns a fleet of coordinated subagents. The update is live for all users in the Claude Code research preview, providing better control over when the agent initiates its autonomous orchestration logic.
We've changed the trigger word from "workflow" to "ultracode". You can still say "use a workflow for this", but when you're clearly referring to something else, Claude won't kick off a dynamic workflow. For an explicit trigger, use "ultracode". We appreciate the feedback!
Still wondering? A few quick answers below.
Every HeadsUpAI update is written based on its original source and reviewed before it's published. Read our editorial standards →
