Editorial illustration for Claude Code adds Tasks for longer agent runs, coordination; can be disabled
Claude Agents Get Long-Running Tasks and Coordination
Claude Code adds Tasks for longer agent runs, coordination; can be disabled
Claude Code just got a lot more autonomous, and a lot harder to ignore. Anthropic’s new Tasks system lets coding agents run longer, coordinate across sessions, and hold a persistent project plan on disk. But enterprises don’t pivot overnight.
That’s why the same update ships with a kill switch: `CLAUDE_CODE_ENABLE_TASKS=false`. Teams can keep their old workflows intact while they figure out how this all fits. The real insight?
Context is the bottleneck. Every developer knows the agony of a cluttered session, performance tanks, reasoning splinters, and clearing the buffer feels like pulling the fire alarm on your own memory. Tasks fixes that.
Store the plan on disk. Run `/clear` or `/compact` without losing the roadmap. Suddenly, “aggressive context management” becomes a best practice, not a gamble.
And behind the scenes, Anthropic is quietly redefining what a coding agent can be. Shorthand arguments, customizable keybindings, these are quality-of-life signals for builders who want to script complex workflows. But the deeper shift is philosophical.
Tasks give Claude Code persistence, dependency tracking, and the stability for long-running background work. This isn’t a copilot anymore. It’s a subagent you can trust to run solo, especially when powered by Claude Opus 4.5.
The future of coding tools just turned into project management.
By giving Claude Code a persistent memory, a way to understand dependency, and the stability fixes required for long-running processes, they have moved the tool from a "copilot" that sits next to you to a "subagent" that can be trusted to run in the background — especially when powered by Anthropic's most performant model, Claude Opus 4.5.
Here’s the outro: Tasks are not just a feature update. They are a declaration of intent: Anthropic sees the coding agent as a resident engineer, not a summoned assistant. For teams wary of disruption, the kill switch, `CLAUDE_CODE_ENABLE_TASKS=false`, is a lifeline, not a hedge.
It buys time to retool workflows, to observe how persistent context and subagent coordination reshape the development cadence. But the direction is clear. Once you trust an agent to hold the plan across sessions, to manage its own context economy, to carry a refactor from one terminal window to the next without forgetting the why, you stop treating it as a tool.
You treat it as a partner. And that changes everything from how you build to how you define your own role in the process.
Related Reading
Browse all Anthropic news →
LLMs & Generative AI ChatGPT's 'Nerdy' tweak rewards goblin metaphors in answers, study finds
LLMs & Generative AI Google tests visual 'magazine-style' UI for Gemini 3 Pro users
LLMs & Generative AI AI Engineers Face Rising Costs, Need New Strategies for Efficiency
Related Topic Trump cracks down on Anthropic after Amazon tip; staff largely foreign
Open Source
Related Topic Claude Mythos highlights EU AI safety gaps, says researcher Caroli
Policy & Regulation
From Archives Anthropic adds Slack, Figma, Asana to Claude, touts AI as job substitute
From Archives MCP links Claude chat to Slack, Canva, Figma and adds Box, Clay integrations
From Archives Claude for Excel opens the gates; Tasklet AI agent links to any app
From Archives Anthropic expands Claude Cowork to paid tiers, enabling team‑wide AI workflows
Common Questions Answered
How does the new Tasks feature in Claude Code enable longer-running agents?
The Tasks feature allows a single agent to persist across multiple calls, maintain state between sessions, and hand off work to peers. This addresses the previous limitation of agents being confined to short, disconnected interactions, enabling more complex and sustained workflow management.
What is the CLAUDE_CODE_ENABLE_TASKS environment variable and why was it introduced?
The CLAUDE_CODE_ENABLE_TASKS environment variable (in v2.1.19) allows teams to opt-out of the new Task-based system temporarily. This provides flexibility for enterprise teams who need time to migrate their existing workflows, recognizing that not all organizations can immediately adopt the new architectural approach.
How does the Tasks system address the 'context economy' problem for developers?
The Tasks system helps manage context as a critical resource by allowing agents to maintain memory and state across multiple interactions. This approach aims to reduce friction in enterprise deployments by creating agents that can remember not just what to do, but why and in what order.
Further Reading
- Claude Code TASKS (New Upgrade): RIP Ralph Loops — AICodeKing (YouTube)
- Enabling Claude Code to work more autonomously — Anthropic
- Claude Code: Best practices for agentic coding — Anthropic
- Introducing advanced tool use on the Claude Developer Platform — Anthropic
