Claude Code v2.1.318 adds sign-in expiry checks and fixes config and login bugs

Anthropic has released Claude Code v2.1.318, published on 2026-11-04. The update adds account, automation and reporting features and fixes a range of reliability bugs, according to the Claude Code release notes.

On the feature side, the release adds an assume_role option for mantle upstreams in the Claude apps gateway. It supports a role in another AWS account and per-developer AWS cost attribution. Mods can now pass an effort option through a mod’s $.model.fork, so a quick side job can run at low effort whatever effort the session uses. Sign-in visibility also improves: claude auth status now reports loginExpiresAt, and claude -p JSON results include credential_expires_at. Starting 10 days before a stored claude.ai sign-in ends, claude -p text output prints a one-line warning to stderr.

The fixes cover several problem areas. –continue could lose earlier conversation after a malformed tool call’s retries ran out, a regression introduced in 2.1.314. macOS sessions with many running Bash commands could stall while memory grew. Logout and MCP config changes could report success on a shared network home directory when the config file could not be updated. Jobs could also exit with “Not logged in” when the same account was signed in elsewhere.

Why it matters

Teams that run Claude Code in scripts or on shared machines get clearer warnings before sign-ins expire and fewer silent failures. The config and login fixes matter most where changes could appear saved when they were not.

What to do

Update to v2.1.318 and run claude auth status to see when your stored claude.ai sign-in ends. Confirm remaining limits, such as claude mcp add and remove still being able to replace a saved server, on Anthropic’s or Claude Code’s official documentation, since the release notes do not cover every case.