Anthropic released Claude Opus 4.6 on 5 February, and two changes stand out for businesses that automate with AI. The first is a one-million-token context window, now standard on the flagship model. The second is Agent Teams, a way of having multiple AI agents work on the same problem in parallel rather than relying on a single model to do everything in sequence.
We covered the leap that Claude Opus 4 and Sonnet 4 represented for agentic workflows last year. Opus 4.6 continues that trajectory, and the direction it points to matters more than the version number.
What Actually Changed
A One-Million-Token Context Window
A million tokens is roughly 750,000 words. In practical terms, that means a single AI call can now hold an entire contract set, a year of support tickets, or a complete policy manual in working memory at once.
For automation, this removes a constant source of friction. Previously, processing a large document meant chunking it into pieces, running each piece separately, and stitching the results back together, with all the accuracy loss that introduces at the seams. With a context window this large, an n8n workflow can pass a whole document to the model and ask questions across the entire thing without losing the thread.
Agent Teams
The headline feature is Agent Teams, where one lead agent can spin up several specialist agents that work in parallel, share context, and coordinate their outputs. Instead of a single generalist model handling research, drafting, and review one step at a time, you get a researcher, a drafter, and a reviewer working concurrently and checking each other's work.
It is worth being precise about where this sits today: Agent Teams launched as a research-preview capability aimed squarely at software development. It is not a button most businesses press directly. But the pattern it formalises, multiple specialised agents collaborating on one task, is exactly the pattern that automation platforms have been moving towards, and it is becoming practical for production business workflows.
Why Multi-Agent Matters for Automation
For years, the standard way to add AI to a workflow was a single model call: send a prompt, get a response, move on. That works well for narrow tasks. It struggles when a task has several distinct sub-jobs that each need different judgement.
Multi-agent design splits the work the way a team of people would:
- One agent extracts and structures the raw information
- Another applies business rules and makes a recommendation
- A third checks the recommendation against policy before it goes anywhere
This division of labour does two useful things. It improves quality, because a reviewer agent catches mistakes a single pass would miss. And it improves transparency, because each agent's output is a checkpoint you can log, audit, and override.
Practical Impact on Business Workflows
Document-Heavy Processes
Consider a professional services firm reviewing supplier contracts. A million-token window lets the model read the full contract plus the firm's standard playbook in one pass. A multi-agent approach then has one agent summarise key clauses, a second flag deviations from the playbook, and a third draft a plain-English risk note for the partner. Each step is reliable enough to trust with human review only on the flagged items.
Multi-Step Customer Operations
In an n8n workflow that handles inbound enquiries, specialist agents can classify intent, retrieve the right account context, draft a response, and verify that the draft does not promise anything outside policy, all before a human ever sees it. The verification step is the part that makes this safe to run at volume.
Smarter Retool Applications
A Retool operations dashboard backed by Opus 4.6 can now reason over far more data per request. A manager can ask a complex, open-ended question and have the AI work across the full dataset rather than a truncated sample, with a second agent sanity-checking the numbers before they are presented.
Faster, Higher-Quality Knowledge Work
Beyond structured processes, the combination of a large context window and multi-agent review changes the economics of knowledge work that used to be too nuanced to automate. A marketing team can have one agent draft, a second fact-check against approved sources, and a third align the tone to brand guidelines, producing a near-final draft that a person polishes rather than writes from scratch. The human stays firmly in the loop; the blank-page problem disappears.
When Opus 4.6 Is Worth the Premium
Capability is only half the decision. Opus 4.6 sits at the top of the price range, so the practical question for any workflow is whether the task genuinely needs it.
It is worth the premium when:
- The task requires reasoning across a large body of context that a smaller model would have to chunk and risk getting wrong.
- Several agents need to collaborate and challenge each other to reach a reliable result.
- The cost of an error is high enough that the quality difference pays for itself.
It is not worth it when a lighter model does the job just as well. Classification, simple extraction, routing, and routine drafting rarely justify a frontier model. The most cost-effective designs we build route the bulk of the volume to cheaper models and reserve Opus 4.6 for the genuinely hard steps, the same tier-the-model-to-the-task logic we explored with OpenAI's tiered GPT-4.1 family.
The headline number on a model release is rarely the number that matters. What matters is whether it makes a specific process in your business measurably more reliable or more capable than it was, at a cost that makes sense.
What to Watch For
More capable models do not remove the need for sound workflow design. The pitfalls we see most often:
- Multi-agent where single-agent would do. Agents add coordination overhead and cost. Use them when a task genuinely has distinct sub-jobs, not because the architecture sounds impressive.
- Confusing a bigger context window with better judgement. A million tokens means the model can read more. It does not mean it will weigh everything correctly. Test on your own documents.
- Skipping the review step. The reviewer agent is what makes multi-agent worth it. Cutting it to save a model call defeats the purpose.
- Ignoring cost. Opus 4.6 is powerful and priced accordingly. Reserve it for genuinely complex work and route routine steps to lighter models.
Our Take
Opus 4.6 is not a revolution so much as a consolidation. The large context window removes a practical headache that has constrained document automation, and Agent Teams puts an official name and a clear design pattern on something that was already proving its worth: letting several specialised agents collaborate instead of asking one model to do everything.
For most Australian SMEs, the takeaway is not to chase the newest feature. It is to recognise that the building blocks for reliable, auditable, multi-step AI automation are now mature enough to deploy with confidence.
If you want to understand which of your processes would benefit from a multi-agent approach, our automation readiness assessment is a good starting point, and our team has hands-on experience integrating Claude models into n8n and Retool workflows.
The gap between an impressive AI demo and a dependable production system keeps narrowing. Opus 4.6 narrows it a little further.