Claude Code 2.1.291 Fixes Cloud Permission Replies and Lost Final Messages

Anthropic published Claude Code 2.1.291 on October 6, 2026, reporting fixes for dropped cloud permission replies and final messages lost at exit.

Users on affected builds should prioritize the corrected version and preserve important visible output before restarting. For cloud workflows, check both the client installation and the session runtime; updating one does not establish the other’s version.

Two regressions, different failure points

Anthropic’s release notes identify the introduction versions as follows:

The notes do not give a complete affected-version or platform matrix, failure frequency, or a recovery method. They describe lost conversation content, not erased source files or commits; the approval issue is not described as a permission bypass.

At 04:52 UTC on October 6, npm’s distribution tags pointed latest to 2.1.291 and stable to 2.1.285. Since that stable version predates both stated introduction versions, these two regressions alone are not a reason for someone still on 2.1.285 to switch channels. That is a version-based inference, not a general assurance about the older build.

Update the runtime that does the work

• Local installation: check claude --version; where supported, /status shows the active session’s version. For native installs, use claude update within the configured channel, then relaunch and confirm the version. Package-manager installs need their own update command. Anthropic’s setup guide distinguishes these paths; an “up to date” result on stable does not necessarily mean 2.1.291.

• Self-hosted cloud environment: session processes normally use the runner’s binary, with session auto-updates disabled. Anthropic’s deployment instructions require installing the newer host binary or rebuilding the image, then restarting runners. Preserve active work and use the fleet’s established drain/restart process. If a custom session executable is configured, check its version too.

• Anthropic-hosted cloud session: execution happens on Anthropic’s infrastructure. That separation means a laptop upgrade cannot confirm the remote runtime has changed. The reviewed sources do not establish when the hosted fleet received 2.1.291 or provide a user-controlled rollout switch.

For fleet deployment context, see RohitAI’s Claude Code self-hosted runner analysis.

Preserve the handoff before quitting

Before ending an older session, save important visible answers or handoff notes separately. Where available, the documented /export command writes the conversation as plain text; inspect the saved content before relying on it. This is a precaution, not a tested workaround or a way to recover messages already missing.

Keep the intended approval policy: bypassPermissions changes which prompts appear, not whether replies are delivered correctly. If an operation’s outcome is unclear, inspect tool results and repository changes before repeating it; a missing message alone does not establish whether the action ran.

Reporting note: This AI-assisted brief draws on Anthropic’s release notes, current documentation and npm metadata checked October 6, 2026. No hands-on testing was performed; fix effectiveness has not been independently verified.