{"slug": "five-betas-went-ga-which-headers-can-you-delete-now", "title": "Five Betas Went GA. Which Headers Can You Delete Now", "summary": "Anthropic's Claude Developer Platform brought five capabilities to general availability on August 19, 2026: computer use, browser use, the Files API, Agent Skills with the Skills API, and Admin API user management for Claude Enterprise. No sunset dates are published for superseded beta headers, and old identifiers remain supported, but upgrading to the GA computer use toolset (computer_toolset_20260801) changes behavior by batching actions, adding 17 member tools, and enabling zoom by default, while dropping the Files API beta header (files-api-2025-04-14) requires code changes for list pagination.", "body_md": "The Claude Developer Platform had a maintenance day on August 19, 2026 — and for teams running Claude integrations in production, that is better news than a feature day. Five capabilities reached general availability at once: computer use, browser use, the Files API, Agent Skills with the Skills API, and Admin API user management for Claude Enterprise.\n\nThe instinctive question for any integration owner reading a GA announcement is “what breaks, and by when?” Here the answer is unusually calm: nothing breaks, and no deadline exists. Every beta header these GA moves supersede is still accepted for backward compatibility, earlier beta tool versions remain available, and — after checking both Anthropic’s general beta-header policy page and each individual release note — we can say no sunset date is published for any of them.\n\nThis is not another how-to. We already publish implementation guides for computer use and Agent Skills, and we cross-link them below. This post does the maintenance-day job instead: exactly what changed, which headers you can delete, what silently keeps working if you do nothing, and the one place where upgrading changes behavior underneath a same-looking call.\n\n- 01Five capabilities reached GA in one day.Computer use, browser use (a genuinely new toolset), the Files API, Agent Skills plus the Skills API, and Admin API user management all left beta on August 19, 2026, per Anthropic’s release notes.\n- 02Nothing here is a forced migration.The old beta headers are still accepted on all three header-dropping capabilities, and earlier beta tool versions such as computer_20251124 remain available. The GA identifiers are additive.\n- 03No sunset date is published — and that absence matters.As of the date checked, neither the beta-headers policy page nor any individual release note states when superseded identifiers stop working. You can schedule this migration on your own calendar, not Anthropic’s.\n- 04Computer use changes behavior, not just its header.computer_toolset_20260801 batches multiple actions per turn, ships 17 member tools, and turns zoom on by default. Teams upgrading purely to drop the header inherit a new default without asking for it.\n- 05The Files API is the one place where deleting the header alone forces a code change.Dropping the files-api-2025-04-14 header switches list pagination from cursors to page/next_page with a new ids[] filter, and adds file expiration. List-files code needs a small, real update.\n\n## 01 — What Went GAFive moves, one day — read it as a *maintenance* release.\n\nThe [August 19 release-notes entry](https://platform.claude.com/docs/en/release-notes/overview) reads as five bullets, but they are not five equal stories. Four of them retire beta headers or beta tool versions for capabilities teams already run in production. One — browser use, shipping as `browser_toolset_20260801`\n\n— is a genuinely new tool that drives a browser your application hosts through its accessibility tree, and it deserves its own treatment: our [deep dive on the new browser use tool](/blog/anthropic-browser-use-tool-ga-new-agent-toolset) covers it in full, so here it gets exactly one row in the table below.\n\nThe table is the checklist version of the whole event: what the old identifier was, what the GA identifier is, what actually changes beyond the header, and whether you need to do anything this quarter.\n\n| Capability | Superseded identifier | GA identifier | What actually changes | Action needed |\n|---|---|---|---|---|\n| Computer use | `computer_20251124` — still supported; a beta header is still required on most other platforms | `computer_toolset_20260801` , no beta header on the Claude API | Batched multi-action turns, 17 member tools, zoom on by default, per-member `configs` , new request/response shape | Review the zoom default and the new tool_result contract before upgrading — or change nothing |\n| Browser use | None — new tool | `browser_toolset_20260801` | New client toolset driving an app-hosted browser via the accessibility tree; not a rename of computer use | Evaluate separately — see our dedicated browser-use post |\n| Files API | `files-api-2025-04-14` beta header | `/v1/files` , no header required | File expiration; pagination moves from cursors to `page` / `next_page` ; new `ids[]` filter | Update list-files pagination code when you drop the header |\n| Agent Skills + Skills API | `skills-2025-10-02` beta header | `/v1/skills` , no header required | None stated beyond the header — requests that still send it continue to work unchanged | None required |\n| Admin API user management | `ce-user-management-2026-07-13` header — required only on group and custom-role requests | GA for members, invites, groups, and custom roles (Claude Enterprise) | Header no longer required on group/custom-role requests; requests that still send it are accepted unchanged | None required |\n\nOne framing note before the detail: the pattern across all five moves is identical. Old headers are *accepted*, not rejected. A request that still sends `files-api-2025-04-14`\n\nkeeps working and returns the previous response format; a request that still sends the Skills or user-management header behaves identically to one that does not. That single design decision is what turns a five-item changelog into a calm afternoon instead of a sprint-planning emergency.\n\n## 02 — Computer UseThe header is gone — and the *behavior* changed with it.\n\nComputer use leaves beta on the Claude API as the `computer_toolset_20260801`\n\ntoolset. The headline is the missing beta header, but the more consequential story is that this is a structural revision, not a rubber stamp. Where the beta tool was one monolithic tool with an `action`\n\nfield, the GA toolset exposes **17 member tools** for screenshot, mouse, and keyboard control of a desktop environment, per the [Computer Use Tool reference](https://platform.claude.com/docs/en/agents-and-tools/tool-use/computer-use-tool).\n\n\"The computer use tool is out of beta on the Claude API as the `computer_toolset_20260801` toolset: no beta header, batch actions (several actions in one turn), `zoom` enabled by default, and per-member configuration through `configs`. Earlier beta versions remain available.\"— Claude Platform release notes, August 19, 2026\n\nThree of those clauses deserve unpacking, because each one changes what your integration code sees:\n\n### Batch actions: multi-action turns\n\nClaude can now return several `tool_use`\n\nblocks in a single response — click, type, screenshot — without waiting for each intermediate result. Execution is strictly sequential, not parallel. The subtle new obligation is in error handling: if one block fails, execution stops there, but **every subsequent block in that turn must still receive a tool_result**, with content stating it was not executed because an earlier action failed. Harness code written for the one-action-per-turn beta has never needed to fabricate results for skipped actions; the GA toolset requires it.\n\n### Zoom: on by default\n\nThe zoom tool lets Claude request a cropped, full-resolution view of a screen region — useful for small text, dense UI, file names, or status-bar content — while the coordinates it uses afterward stay in full-screenshot space. Anthropic’s docs are explicit that zoom is enabled by default for all 17 member tools. It can be switched off per integration via `configs`\n\nif your environment cannot produce zoomed images, but the toolset ships with it on.\n\n### A new request/response shape\n\nUpgrading is a real (if small) migration, documented in the reference’s own migration table: the display parameters (`display_width_px`\n\n, `display_height_px`\n\n, `display_number`\n\n) are no longer needed because coordinates are always in screenshot pixel space; `tool_use`\n\nand `tool_result`\n\nblocks now carry a `toolset_name`\n\nfield and dispatch on the toolset-name plus tool-name pair instead of a single `action`\n\nfield; and zoom moves from an `enable_zoom`\n\nparameter to a built-in member tool.\n\n*computer_toolset_20260801*purely to delete the beta header gets a new capability — zoom — turned on without asking for it. That is the sharpest distinction in this whole GA batch: “beta header removed” and “default behavior changed” arrived in the same identifier. If your environment cannot serve zoomed screenshots, set\n\n`configs`\n\nto disable zoom explicitly, or stay on *computer_20251124*, which remains supported.\n\nTwo scoping caveats keep this honest. First, the no-beta-header behavior is **Claude API only**: as of the date checked, Claude Platform deployments on AWS, Amazon Bedrock, Google Cloud, and Microsoft Foundry still require a beta header or only offer the earlier tool versions. Second, the GA toolset is supported on Claude Fable 5, Claude Mythos 5, Claude Opus 5, Claude Sonnet 5, and Claude Opus 4.8 — the same five-model list the release notes give for browser use.\n\nNone of this changes how you should build a computer-use agent — for that, our [computer use API build guide](/blog/anthropic-computer-use-api-guide) and [production deployment guide for computer use](/blog/claude-computer-use-production-deployment-guide) remain the implementation references, and our [cross-vendor computer-use agent matrix](/blog/computer-use-agents-2026-claude-openai-gemini-matrix) covers the competitive picture. What GA changes is the operational posture: this surface is no longer experimental by Anthropic’s own labeling, and the toolset revision is the shape new work should target.\n\n## 03 — Files APIThe one place your code *actually* needs touching.\n\nThe Files API is GA on the Claude API: requests to the `/v1/files`\n\nendpoints, and Messages API requests that reference an uploaded file, no longer require the `files-api-2025-04-14`\n\nbeta header. Requests that still send it keep working and return the previous response format. But of the five GA moves, this is the one where dropping the header changes what comes back — which makes it the most concrete code-touch in the release, and the item most secondary coverage will likely skip past in favor of the flashier toolsets.\n\n### Pagination changes shape\n\nWithout the beta header, the list endpoint moves from cursor-only pagination to `page`\n\n/ `next_page`\n\npaging, plus a new `ids[]`\n\nfilter, per the [Files API guide](https://platform.claude.com/docs/en/build-with-claude/files). The defaults: 20 files per page, 1,000 maximum, newest first. The `ids[]`\n\nfilter is genuinely useful — check up to 100 known file IDs in one request without paging — but it carries a quiet gotcha: any ID that does not resolve is silently omitted from the response rather than raising an error, so callers must diff the returned IDs against the requested ones to detect misses. It always returns a single page (`next_page`\n\ncomes back null) and cannot be combined with `page`\n\nor `limit`\n\n.\n\n### File expiration is new\n\nGA also brings a real lifecycle feature: set `expires_in_seconds`\n\nat upload, from 3,600 seconds (one hour) to 7,776,000 seconds (90 days). The resulting `expires_at`\n\ntimestamp is null if no expiration was set, and the value is fixed at upload — it cannot be changed afterward. Once `expires_at`\n\npasses, downloading the file’s content returns a 404 and a Messages request referencing it fails before inference runs. But metadata stays readable for up to 30 days past expiration, and the file keeps appearing in list responses during that window — so list-consuming code has to compare `expires_at`\n\nagainst the current time to filter expired files out itself.\n\n##### expires_in_seconds range\n\nFrom 3,600 seconds (one hour) up to 7,776,000 seconds. Set once at upload, immutable afterward; expires_at is null when no expiration was set.\n\n##### Per list request\n\nOne request, one page, no paging. Unresolved IDs are silently omitted rather than erroring — diff the response against your request to detect misses.\n\n##### Metadata retention window\n\nExpired files keep appearing in list responses and keep readable metadata for up to 30 days. Content downloads 404 immediately; Messages requests fail before inference.\n\n*content becoming inaccessible*— not as a guaranteed-purge control. If a compliance regime requires provable destruction timelines, this feature alone does not deliver that, and your data-retention documentation should say so.\n\nThe operational numbers worth pinning to your runbook: file storage caps at 500 MB per file and 1 TB per organization; file-related calls are rate-limited to roughly 500 requests per minute; and Files API operations themselves — upload, download, list, get metadata, delete — are free. Only file content used inside Messages requests is billed, as input tokens.\n\n## 04 — Skills + Admin APITwo clean GAs — and one *precisely* scoped header change.\n\n[Agent Skills](https://platform.claude.com/docs/en/agents-and-tools/agent-skills/overview) and the Skills API (`/v1/skills`\n\n) are GA on the Claude API. Requests — including Messages API requests that load Skills through the `container`\n\nparameter — no longer require the `skills-2025-10-02`\n\nbeta header, and requests that still send it continue to work unchanged. That is the entire delta: no behavior change, no new response shape. If you are building with Skills rather than just maintaining them, our [Agent Skills framework guide](/blog/claude-agent-skills-framework-guide) is the authoring deep dive.\n\nThe Admin API move needs more precision, because it is easy to over-generalize. What reached GA is Claude Enterprise user management across all four resource types — members, invites, groups, and custom roles. The header change, though, is scoped: the `ce-user-management-2026-07-13`\n\nbeta header is no longer required specifically on **group and custom-role requests**. Member and invite endpoints never needed that particular header in the first place — they only ever required `anthropic-version`\n\n. So the accurate sentence is “user management is GA, and the one header it ever required is now optional,” not “the Admin API no longer needs any beta header.”\n\n[user-management docs page](https://platform.claude.com/docs/en/manage-claude/user-management), which carries the GA language verbatim: “Group and custom-role requests don’t require the\n\n`anthropic-beta: ce-user-management-2026-07-13`\n\nbeta header. Requests that still send it are accepted and behave identically.” Summaries of the broader Admin API index can lag behind the per-feature pages — the dedicated page and the release notes agree, and they are the sources of record here.## 05 — The Missing DeadlineNo sunset date is published — and that *absence* is the operative fact.\n\nWe checked this two ways, because it is the question every integration owner actually has. First, Anthropic’s general [beta headers reference](https://platform.claude.com/docs/en/api/beta-headers) carries only generic policy language — beta features “may” have breaking changes with notice, be deprecated or removed, or carry different limits — with no dates and no per-feature sunset table. Second, each individual GA release note explicitly says the old header or version “remains available,” “continues to work unchanged,” or is “accepted unchanged,” again with no stated end date. As of the date checked, no sunset or deprecation date is published for `computer_20251124`\n\n, `files-api-2025-04-14`\n\n, `skills-2025-10-02`\n\n, or `ce-user-management-2026-07-13`\n\n.\n\nRead that absence carefully in both directions. It does not mean these identifiers are supported forever — Anthropic’s own policy language reserves the right to deprecate with notice. It means the migration is **yours to schedule**: there is no externally imposed deadline forcing this into the current sprint. A useful mental model is the naming convention itself. Beta headers follow `feature-name-YYYY-MM-DD`\n\n, where the date marks when that beta surface was released — each one is a dated snapshot of an API surface, not a version number. GA froze those snapshots in place and made the current surface the default; it did not detonate them.\n\nOur interpretation: this release pattern — additive identifiers, accepted legacy headers, no published sunsets — is Anthropic optimizing for enterprise trust at exactly the moment these capabilities move from experiments to production dependencies. Whether that posture holds across future releases is not something a single release-notes entry can establish, so the rational response is neither panic nor complacency: put the migration in next quarter’s backlog with a note to re-check the release notes for deprecation announcements before deprioritizing it again.\n\n## 06 — Same-Day AdjacentThree smaller items from the *same* release-notes entry.\n\nThe August 19 entry carried three adjacent changes worth one clause each. Managed Agents sessions gain `allowed_domains`\n\nand `blocked_domains`\n\nconfiguration restricting which sites a session’s `web_search`\n\nand `web_fetch`\n\ntools can reach, set inside the `agent_toolset_20260401`\n\n`configs`\n\narray — with `web_fetch`\n\nalso gaining `max_content_tokens`\n\nand `web_search`\n\ngaining `user_location`\n\n. Managed Agents sessions running in a self-hosted sandbox can now attach memory stores, with the Python, TypeScript, and Go SDK workers downloading each attached store into the sandbox at its `mount_path`\n\nand syncing changes back. And the Claude Console’s session viewer was redesigned with a timeline minimap, per-model-request transcript grouping, and an Inspector panel.\n\nFor the Managed Agents backdrop — effort controls, webhooks, and how Skills plug into sessions — our [Managed Agents update roundup](/blog/claude-managed-agents-update-effort-webhooks-skills) covers the surface these domain controls now bolt onto.\n\n## 07 — Upgrade ChecklistWhat to do this quarter, by *workload*.\n\nWith no deadline forcing the issue, the right move differs by what you run. Four common situations, four different answers:\n\n##### Upgrade deliberately, not casually\n\nThe GA toolset changes the request/response shape, requires tool_results for skipped batch actions, and turns zoom on by default. Test in staging with the zoom default reviewed, or stay on computer_20251124 — it remains supported.\n\n##### One *small* real PR\n\nDropping the header switches list pagination to page/next_page and unlocks the ids[] filter plus expiration. This is the only spot where deleting the header alone forces a code change — schedule it with the header deletion, not before.\n\n##### Delete headers at leisure\n\nBoth GAs are pure header removals with identical behavior either way. Clean the headers out in your next routine dependency pass; nothing changes underneath, and requests that still send them are accepted unchanged.\n\n##### Nothing to delete yet\n\nThe no-beta-header behavior is Claude-API-only as of the date checked. Cloud-platform deployments still require beta headers or only offer earlier tool versions — track your platform’s own docs before editing anything.\n\nLooking forward, the same-day GA of computer use and browser use is the signal worth projecting from: Anthropic now treats agent-environment control — desktop and browser — as a stable, supportable product surface rather than a research preview. Teams that deferred computer-use projects on “it’s still beta” grounds have lost that reason, and the sensible next step is a scoped pilot rather than a platform-wide commitment. If you are deciding which of these surfaces belongs in your automation roadmap — and which workloads justify an agent that drives a screen at all — our [AI transformation engagements](/services/ai-transformation) start with exactly that evaluation.\n\n## 08 — ConclusionA GA day that respects your *backlog*.\n\n### Five GAs, zero deadlines — schedule the migration on your calendar, not Anthropic’s.\n\nAugust 19, 2026 moved five Claude Developer Platform capabilities out of beta in one day, and the operative facts are the calm ones: every superseded beta header is still accepted, earlier tool versions remain available, and, as of the date checked, no sunset date is published for any of them. For integration owners, that converts a five-item changelog into a *prioritization choice* rather than an obligation.\n\nThe two items that earn attention beyond header cleanup are specific. Computer use’s GA toolset changes behavior — batched turns with a new tool_result contract, and zoom on by default — so upgrading is a deliberate act, not a find-and-replace. And the Files API’s pagination change is the one place list-handling code genuinely needs a small update when the header comes out. Everything else — Skills, Admin API user management — is a header you can delete whenever it suits you.\n\nThe broader signal: platforms win enterprise workloads with boring reliability, and this is what boring reliability looks like in a release note. Additive identifiers, accepted legacy headers, and an honest absence of deadlines. Put the migration in the backlog, re-check the release notes each quarter for deprecation announcements, and spend the urgency you just saved on the capabilities themselves.", "url": "https://wpnews.pro/news/five-betas-went-ga-which-headers-can-you-delete-now", "canonical_source": "https://www.digitalapplied.com/blog/claude-platform-betas-ga-computer-use-files-skills", "published_at": "2026-08-19 00:00:00+00:00", "updated_at": "2026-08-23 07:13:32.294926+00:00", "lang": "en", "topics": ["ai-products", "ai-tools", "ai-infrastructure"], "entities": ["Anthropic", "Claude Developer Platform", "Claude Enterprise", "Files API", "Agent Skills", "Skills API", "Admin API", "computer_toolset_20260801"], "alternates": {"html": "https://wpnews.pro/news/five-betas-went-ga-which-headers-can-you-delete-now", "markdown": "https://wpnews.pro/news/five-betas-went-ga-which-headers-can-you-delete-now.md", "text": "https://wpnews.pro/news/five-betas-went-ga-which-headers-can-you-delete-now.txt", "jsonld": "https://wpnews.pro/news/five-betas-went-ga-which-headers-can-you-delete-now.jsonld"}}