Claude Code v2.1.318 Fixes --continue Regression, Stalled macOS Sessions, and 30+ Bugs

Claude Code v2.1.318 is out with more than 30 fixes, plus a handful of additions around authentication expiry and gateway configuration. The headline fix patches a regression introduced in v2.1.314: --continue could lose the earlier conversation after a malformed tool call's retries ran out.

Auth and Gateway Changes

• A stored claude.ai sign-in's expiration date now shows in claude auth status as loginExpiresAt and in claude -p JSON results as credential_expires_at.
• Text output from claude -p now prints a one-line stderr warning starting 10 days before that sign-in expires.
• assume_role is now supported on mantle upstreams of the Claude apps gateway, for cross-account AWS roles and per-developer cost attribution.
• Mod forks support an effort option ($.model.fork) so a quick side job can run at low regardless of the session's effort level; the result reports the effort sent.

Runtime and CLI Fixes

• macOS sessions with many running Bash commands no longer stall while memory grows.
• Permission prompts no longer get answered by keys typed just after sending a message or before a slow prompt appears.
• /logout, claude auth logout, and claude mcp remove no longer report success when the config file couldn't be updated on a shared network home directory. Trust, consent, and MCP setting changes are no longer dropped silently in that case.
• claude mcp add and remove now take the config lock — they wait for it or exit 1. Note: another job's save can still replace a saved server.
• claude plugin commands no longer exit before a slow token refresh is saved, which could sign users out on the next run.
• claude plugin validate no longer passes a custom-named marketplace file that claude plugin marketplace add rejects.
• stdio MCP servers that exit during the version probe are no longer re-probed on every start; servers dying in under 3 seconds for their own reason are pinned to the legacy handshake for 7 days.

Headless, Cloud, and Session Fixes

• Custom slash commands that fail, or that only Claude can invoke, now print output in claude -p and SDK sessions.
• claude -p and Agent SDK sessions no longer report success when an API error cut off a reply while a mod hooked turn.step.
• In headless sessions, Stop now cancels a message sent right after a model change, as it would a queued message.
• Deleted session transcripts are no longer re-created with their last prompt when an idle non-interactive session exits.
• Cloud sessions stopped mid-turn when uploads were refused for several minutes now keep going.
• Setup hook variables written to CLAUDE_ENV_FILE now reach the Bash tool in some cloud sessions.
• Shell commands approved after a self-hosted runner or cloud session restart now run in the folder they were asked in, not the session's start folder.

Also Fixed

• Jobs exiting with Not logged in when another terminal or host signs in again to the same account and org on the same home.
• Sessions refused at startup by an allowedProviders list stored by another login on the same machine.
• Idle compaction replacing a conversation with a reply that wasn't a summary.
• The "Now using usage credits" notice reappearing every ~30 seconds while a background subagent runs.
• claude remote-control hosts, the background daemon, and self-hosted runners failing to start sessions (spawn ENOENT) after version cleanup removed a still-running process's binary.
• Version cleanup treating a running Claude Code process owned by another user (e.g. from sudo claude) as dead and deleting its binary.
• /remote-control showing a session as available after a failed connection.
• /design revoke reporting success on a 404.
• iPhone app showing a cloud session's turn as finished while it kept running.
• Restarted sessions re-sending a failed message ahead of a newer queued one, or dropping an interrupted turn right after reading a large image.

Upgrade with your usual package manager; the release is tagged v2.1.318 on the main branch.