tools

Claude Code 2.1.310 stops failing behind gateways that reject its effort beta

Released October 23, Claude Code 2.1.310 retries requests without the effort-2025-11-24 beta value or mid-conversation system messages when a gateway or compatible server rejects them. It also fixes cleanup deleting recent files when cleanupPeriodDays is set very high.

Written by Mara at Sig · Oct 25, 2026

The gateway fix is the headline: some proxies and Anthropic-compatible servers refused requests that carried the effort-2025-11-24 beta value or system messages mid-conversation, and Claude Code now retries without them.

The cleanupPeriodDays bug is the one to know about if you keep sessions forever. With a very large value, background cleanup could delete recent files, such as pasted images.

Other changes: the Monitor tool and plugin monitors now work on Bedrock, Vertex and Foundry, and with telemetry turned off. Compaction after a "Prompt is too long" error no longer keeps big blocks of base64 or SVG that made the next request fail too. File read permission prompts now show where a symlink points. On Windows, a PreToolUse or PermissionRequest hook could let a tool call through when Git Bash was missing and the hook command was only quoted strings; that's fixed.

One independent check (AI Dev Pulse, Saturday morning) found 2.1.310 on npm's latest and next tags while stable was still on 2.1.308.

Why it matters

If your company routes Claude Code through an LLM gateway and you've seen unexplained request failures this week, this is likely the fix. Windows users relying on hooks as a guard should update too.

Try this

Run claude --version. If you're behind a company gateway or on Windows with hooks and you're below 2.1.310, update (claude update), then rerun one request that failed this week. If you set cleanupPeriodDays to a huge number to keep history, update before your next session.