Anthropic's August Housecleaning: Export Your Workbench Prompts Before August 17

The legacy Anthropic Workbench and its companion experimental API endpoints (/generate_prompt, /improve_prompt, /templatize_prompt) retire August 17 — saved prompts and evals won't transfer.

If your team uses the legacy Workbench in the Anthropic Console, you have until August 17 to export saved prompts, variable templates, and eval runs. None of those persist in the replacement.

What changes August 17:

• Workbench (legacy) disappears from the Console for all users. Saved prompts, variables, and evals are not supported in the updated Workbench.
• /v1/experimental/generate_prompt, /v1/experimental/improve_prompt, /v1/experimental/templatize_prompt — these routes return an error after removal. Update any automation that calls them.

The replacement Workbench is a simpler, stateless interface built directly on the public Messages API. What you construct there is the exact JSON payload you'd send from code — no abstraction layer. Better for copy-paste into your app, but nothing persists between sessions.

Also in the August release notes: The Claude API no longer bills you when a request returns stop_reason: "refusal" with no output generated — a welcome change for safety-gated workloads. And the advisor tool now accepts a max_tokens cap to reduce latency on calls that don't need a full-length response.

Why it matters: If you've built prompt templates or eval baselines inside the legacy Workbench, the clock is running — export anything you want to keep before August 17.

Sources: Claude Platform Release Notes · Anthropic Workbench Help