Expected: Anthropic Retires Legacy Workbench and Prompt Tools APIs
The August 17 cutoff affects saved legacy prompts, evals and three experimental prompt endpoints, while Anthropic's updated Workbench uses a reduced persistence model.
Anthropic scheduled the legacy Workbench in Claude Console to lose access on August 17, 2026, alongside three experimental prompt-tools APIs. Developers who kept prompts or evals in the older interface, or who call the generate, improve and templatize endpoints, face a migration checkpoint today. Anthropic's official pages establish the timetable and the affected surfaces, but they do not say that the cutoff completed at a specific hour, so this remains an expectation rather than confirmed removal.
The practical change is broader than a renamed page. Anthropic says the updated Workbench remains a place to test Claude models and API features, but it does not preserve prompt history or support prompt evaluation in the way the legacy tool did. Teams using the old storage or experimental automation need to separate what must be exported from what must be rebuilt against supported API workflows.
What is known
Anthropic's Claude Platform release notes announced on July 17 that legacy Workbench access would end on August 17. The same entry says saved prompts, variables and evals are not supported in the updated Workbench, and directs users to export data through the retirement banner or Organizational Settings.
The release notes also name three experimental API routes scheduled to retire with the old interface: `/v1/experimental/generate_prompt`, `/v1/experimental/improve_prompt` and `/v1/experimental/templatize_prompt`. Anthropic says calls will return an error after removal. That makes the deadline relevant not only to people using Claude Console manually, but also to internal tools that incorporated those experimental endpoints.
Anthropic's Workbench help page adds the data consequence. It says the legacy version was already unavailable to new users and that, after the retirement date, its stored prompts, prompt versions and evals would no longer be accessible. The page advises exporting material before the cutoff.
How the updated Workbench differs
The current Workbench is built on Anthropic's public Messages API. A request assembled in the interface is intended to match the request a developer would send from code, and the interface can export the tested request as a code snippet. It is therefore still useful for inspecting request and response structure, trying models, adjusting parameters and testing tool definitions.
Its persistence model is deliberately lighter. Anthropic says the updated interface does not store prompts or conversations on its servers: the current draft stays in the browser, and developers can retain a request through the code view. That is not a drop-in replacement for teams that treated legacy Workbench as a shared prompt archive or evaluation workspace.
Why the cutoff matters for API teams
Teams should check two separate dependencies. The first is stored work: prompts, versions, variables and evals that existed only in legacy Workbench may become inaccessible. The second is executable integration: applications or scripts calling any of the three experimental prompt routes need another supported way to generate, refine or template prompts before the endpoints begin returning errors.
Anthropic's pages do not document an automatic transfer of legacy prompt history into the updated Workbench, nor do they provide a compatibility layer for the retiring experimental routes. That leaves migration design with customers: export the material that still matters, preserve it in a controlled repository, and test replacement workflows through the Messages API or other documented surfaces. Those are operational implications of the announced limits, not a claim that Anthropic has supplied a one-step migration tool.
What would confirm it
Completion would be confirmed by direct loss of legacy Workbench access for previously eligible accounts, error responses from the three retired experimental endpoints, or an Anthropic status or release-note update stating that removal is complete. A delayed cutoff, extended export window or documented migration path would materially change this article.
Evidence quality and limits
Both sources are official Anthropic pages, so the announced scope and migration warning are authoritative first-party evidence. They are not independent evidence, and neither page provides a precise cutoff time, account-by-account rollout detail, observed endpoint response or service-status record proving completion. Internal confidence is therefore medium.
Status
Expectation. Anthropic announced the August 17 retirement, but the final access and endpoint state has not been directly verified.
Sources
Update note: Last reviewed 2026-08-17. We will revise this post when Anthropic confirms the cutoff or changes the migration guidance.
Sources
- Anthropic — Claude Platform release notes — official
- Anthropic — How do I use the Workbench? — official
Drafted with AI assistance from source briefs; reviewed for citation completeness and label accuracy.