The grace period Anthropic offered when it announced its API policy changes earlier this month closed on April 17. Subscribers who intended to claim the company's transition credit — the one meant to cushion the migration away from third-party tooling affected by the OpenClaw cutoff — had to do so before that date. Tuesday is Day Four after the deadline. The question the paper's Monday major on the Cherny concession left open — whether the fix held — is no longer pending. It is an outcome. [1]

On the GitHub side, issue #41788, filed against the Claude Code CLI, tracked a client-side cache regression that was resolved in v2.1.91. [2] Issue #42939, tracking the server-side five-hour-window rate-limit drain that Cherny's April 17 Threads post specifically promised to raise, remains open. Users report the drain is lower than in early April but still higher than pre-April-4 baselines — the period before the OpenClaw third-party-tools change, the v2.1.89 silent limit reduction, and the 200,000-token tool-result truncation. [3]

The arithmetic of compute is not generous to an AI lab in Anthropic's position. Opus 4.7 uses more thinking tokens than Opus 4.6, which used more than Opus 4.5, which used more than Sonnet. Cherny conceded as much in his Threads post. [4] The concession was the news of Monday. The post-concession operational reality — five hours of session time that is still not quite what subscribers were paying for in March — is the news of Tuesday.

One thing worth naming: the subscribers who migrated to Moonshot's Kimi K2.6, to Cursor's agent, or to Google's Gemini for Mac are not coming back on Friday to collect a credit that expired on Friday prior. The migrations are done. The question now is not whether the fix held. It is whether the quarter's compute pressure compresses the transparency back toward opacity by the end of Q2.

-- THEO KAPLAN, San Francisco