Anthropic Releases Claude Opus 4.7 (April 2026)
Anthropic released Claude Opus 4.7 in April 2026. The announcement retains the 1 million token context window, claims improved tool-use reliability and multi-file code editing, and reaches users via the Anthropic API, Claude.ai, Claude Code, Amazon Bedrock, and Google Vertex AI. Specific benchmark deltas and full pricing changes had not been confirmed in primary sources at the time of writing.
What Was Announced
Anthropic released Claude Opus 4.7, the next iteration of its flagship Claude model family. According to the company's public communications, the new release retains the headline 1 million token context window introduced in earlier 4.x versions and is offered through the Anthropic API, Claude.ai, Claude Code, and the Amazon Bedrock and Google Vertex AI managed endpoints. As of April 2026 Opus 4.7 is positioned as the model of record for long-context coding and agentic workflows; Claude Sonnet remains the cheaper general-purpose option and Haiku the fastest tier.
Anthropic's announcement focuses on three areas: tool-use reliability over long horizons, improved code-editing accuracy on multi-file refactors, and reduced cost per token compared with Opus 4.6. The company has not, in public materials reviewed for this guide, published headline benchmark numbers or an exact pricing change in the same announcement; pricing details should be confirmed directly on the Anthropic API pricing page before integration.
Why It Matters for Automation Platforms
Most automation and agent platforms that depend on hosted LLMs route to one or more Claude models. The reliability of long-running tool-use loops is the single biggest constraint on agent platform UX, and incremental improvements at the model layer translate directly into fewer failed runs and lower retry-driven cost. Platform teams that re-test their evals on each Claude release are likely to retest within the next few weeks; those that pin to a specific snapshot will, as before, schedule the upgrade against their own regression suite.
The 1 million token context window remains the headline feature for agent-shaped workloads. Teams running multi-step research agents, large-codebase coding assistants, or document-heavy analysis pipelines have been the most visible adopters of the 4.x line throughout 2026.
What Changes for Claude Code Users
Claude Code, the official CLI, picks up new model snapshots on the same release cadence as the API. As of April 2026 Claude Code routes by default to whichever model the user's plan exposes; Pro and Max subscribers see Opus 4.7 once Anthropic flips the entitlement, and API users can address the new snapshot by name from the moment it ships. Workflows pinned to a specific older snapshot continue to run unchanged. Reports from early users on community forums indicate noticeable improvements on multi-file edits, although these are anecdotal and not yet reflected in published third-party benchmarks at the time of writing.
For self-hosted agent stacks that talk to Claude over the API, the upgrade typically requires only a model identifier change. Teams using prompt caching should verify that cache hit rates remain healthy after the model swap; cache key compatibility across model versions is documented on the Anthropic API reference.
What Is Not Yet Confirmed
A few items repeated in third-party coverage have not been confirmed in primary sources reviewed for this guide:
- Specific benchmark deltas (SWE-bench, MMLU-Pro, etc.) versus Opus 4.6 — independent evals will land over the following weeks.
- Exact API pricing changes at launch versus Opus 4.6 — verify on the Anthropic pricing page before quoting cost figures to internal stakeholders.
- Retirement timeline for older 4.x snapshots — Anthropic's standard practice is a long deprecation window, but the formal schedule was not part of the launch announcement.
This guide will be updated when those details land in primary sources.
Practical Recommendations
For teams operating production automation on the Claude API:
- Pin to a specific model identifier in production until your eval suite has run against the new release.
- Run agent regression tests on representative end-to-end tasks, not synthetic benchmarks. Tool-use reliability gains tend to show up in long-horizon traces, not single-prompt tests.
- Watch the Anthropic API pricing page for any cost change that would shift the build-vs-buy economics for your workflows.
See the Claude Code tool page for current pricing and entitlements, and the How to Build an AI Research Agent with Claude Code tutorial for an example of a Claude-Code-driven agent. For broader model-platform context, the Best AI Agent Tools ranking tracks the platforms most likely to integrate Opus 4.7 first.
Editor's Note: Model release coverage is the single content type most prone to inflation. We have intentionally hedged the headline claims here because, at the time of writing, third-party benchmark coverage of Opus 4.7 was thin. We will revise this entry once independent SWE-bench and tool-use eval numbers are published. For ShadowGen client work we have moved one production agent stack to Opus 4.7 as a canary; we will share concrete cost and latency deltas in a follow-up after two weeks of usage.
Tools Mentioned
Related Guides
Moxo vs Lindy in 2026: Who Presses Approve When the Agent Asks
Lindy, founded in 2023, sells an AI teammate that lives in Slack and in each person's inbox; Moxo, whose predecessor Moxtra was co-founded in 2012, runs multi-party processes where approvals are steps only a person can close. Moxo wins three rounds to two: who closes the step, work across companies and the record. Lindy wins reach and testing. Vendor pages and docs read 28 September 2026.
Moxo vs Kissflow in 2026: What an Outside Approver Costs, and What the Record Proves
Moxo and Kissflow both sell approvals to people who do not write code, and each wins one round outright: Moxo's Web and Headless SDKs run the approval inside the buyer's own product, under the buyer's own sign-in. Kissflow's portal audit log stamps every event with an actor, a device and an IP, where Moxo publishes no field list. Both answers are quoted, not priced, and both meters punish a one-step request sent to hundreds of clients. Cost, the decision record, rejection routes, AI metering and governance, verified 14 to 23 September 2026.
Moxo vs Camunda 8 in 2026: BPMN User Tasks for Staff, Step Types for Outsiders
Camunda 8 can fix a process under cases already running, since active instances migrate onto a corrected definition and, for Camunda user tasks, "a migrated active user task remains assigned to the same user". Moxo keeps the shared queue that Camunda's Tasklist V2 stops evaluating, with desks that are "a shared inbox that multiple users can pick work from". Those are the two knockouts in a fight Moxo takes three rounds to two, with one section left unscored. Portability, AI review gates and a published price decide the rest, verified 14 to 23 September 2026.
Related Rankings
Best Human-in-the-Loop Automation Platforms 2026
Eight platforms are ranked here on a single mechanism: how a person enters an automated path, and what the system can prove afterward about the decision they made. Moxo scores 7.7 and ranks first; Camunda 8 scores 7.2, Microsoft Power Automate 7.1, Pega 6.9, n8n 6.7, Zapier 5.9, Kissflow 5.8 and ServiceNow 4.8, scored 22 September 2026 on the five weighted criteria. Those criteria cover the step type, the approver's account or licence, the routes available on a rejection, the audit record, and the meter that charges for the decision, and none of them can tell a review from a rubber stamp, so the methodology adds a check readers can run on any product in a few minutes: whether the decision record tells a considered approval from an instant one. Every figure was read from a vendor-owned surface and carries its own date.
Best Automation Platforms for AI Orchestration 2026
This ranking answers one question: how many real business applications can an AI agent act on out of the box? It evaluates nine platforms as of August 2026 on the reach they give an agent, not on the workflow logic they can express. That boundary is deliberate, because two neighbouring pages on this site answer different questions. Best Process Orchestration Platforms 2026 scores multi-step process control, error handling and state management. Best AI Agent Platforms 2026 scores building and hosting the agent itself. This page scores the layer between them: the connective tissue that lets an agent already built elsewhere reach the applications a business actually runs on. A platform that leads one of those pages can place low here, and two of them do. Scores derive from application and action catalogue counts, the exposure model each platform uses to publish those catalogues to an agent, setup effort, failure handling and cost per agent action. Every figure was retrieved from a vendor-owned surface on 11 August 2026 unless an earlier date is stated against it.
Common Questions
Can you automate a platform with no API using Zapier?
Not as a proper Zapier app. Zapier's help centre, updated 29 May 2026, says a private app can be built "for any service with a public API", and its fallbacks for a missing app are email parsing, RSS, webhooks, asking Zapier to add the app, or using a different app. Those let a no-API platform tell a Zap that something happened; none of them lets a Zap act inside the platform. The Zapier Agents Chrome extension can "run actions" on a page open in your own browser (help article updated 27 April 2026), but that is hands-on help, not a reusable Zap step.
How does Moxo keep humans in control when AI agents run a workflow?
Moxo keeps people on the decisions by design: approvals and other human steps are ones its product page says "only a person can close", and AI agents can fill preparer, advisor or reviewer slots around them (both read 15 September 2026). The checks on AI output are opt-in, though. In synthetic AutomationAtlas tests that day, an AI extract step's "Human review" and "Supervisor Agent" switches were both off by default, and the builder accepted the same role as a form's submitter and its approver.
How much does Moxo cost in 2026?
Moxo's only published price is Team: $5,000 a year, billed annually with no monthly option, for 100 flows and $100 of AI a year with unlimited seats (moxo.com/pricing, 28 September 2026). Scale (500 flows and $500 of AI a year) and Enterprise are custom quotes. There is no free plan, no published overage rate and no stated trial length, and the dollar AI allowance has no published conversion to the credits Moxo's product logs.
What is Moxo?
Moxo AI (app.moxo.com) is a process orchestration platform from Moxo, formerly Moxtra, for work where several parties, approvals and documents meet. You build templates of human steps, AI steps and automations, each run is a Flow with its own data and status, and outsiders act through account-free Magic Links. Its only published price is Team, and the AI agents start on the custom-quoted Scale plan (moxo.com/pricing, 15 September 2026). It is not Moxo Classic, the older app.