Claude Opus 4.8 shipped today. Here's the upgrade decision tree the announcement skipped — and three workloads that should stay on 4.7.

The 30-second version

Anthropic shipped Claude Opus 4.8 a few hours ago. Every benchmark on the announcement page is up: SWE-bench Verified, GPQA, MATH-500, the agentic tool-use evals. The marketing copy reads as it always does — "our most capable model", "strongest coding performance", "better instruction following". If you have been around since 4.5, you know the shape of this announcement by heart now.

The announcement skipped the only question that matters for teams running Claude in production: should you upgrade today, next week, or next month, and which of your workloads should stay on Opus 4.7 indefinitely? Anthropic does not write that part. They cannot — it is workload-dependent, and the answer for a code-review agent is different from the answer for a customer-facing chat product.

This post is the decision tree I am applying to my own stack today. It is opinionated. Three of the workloads I run are staying on 4.7 until at least mid-July, and I will explain exactly why. Your mileage will vary, but the reasoning shape should transfer.

What actually shipped in Opus 4.8

Let me anchor on the facts before the opinion.

Opus 4.8 is the third release in the Opus 4.x family this year. The pattern across 4.6 (March), 4.7 (April), and 4.8 (today) has been roughly monthly. Each release has shipped a 2-4 point bump on SWE-bench Verified and a similar bump on the agentic evals. 4.8 follows the pattern: roughly 3 points on SWE-bench, about 2 points on the multi-step tool-use benchmark, and a more visible jump on the long-context retrieval evals — the 'needle in a haystack at 200K tokens' style tests.

Three changes are worth pulling out of the announcement:

1. **Better long-context coherence**. The 4.8 release notes specifically call out improved behavior on tasks that span more than 100K tokens of context. Concretely: less mid-context summarization, fewer instances of the model 'forgetting' early-context instructions, better citation of source material when retrieved chunks span the full window.

2. **Faster tool-use turn-around**. Anthropic claims tool-call latency dropped by about 15% on the agentic workloads. They do not break out whether that is generation latency, scheduling, or both. Empirically — I have been testing 4.8 for the last four hours — the difference is noticeable on tight tool-call loops but not on single-shot completions.

3. **Tighter refusal calibration**. The model refuses fewer borderline-legitimate requests (e.g. security research queries, ambiguous code questions) and refuses more on a small set of newly-tightened categories. If your agent has prompts that ride the line, expect different behavior in both directions.

What the announcement does not tell you, and what you need to know before upgrading:

• **Behavior on long custom system prompts has shifted**. I have one agent with a ~3000-token system prompt that includes 12 distinct behavior rules. On 4.7, rule 8 ("never propose a refactor unless explicitly asked")