Moving a session to the background now carries queued prompts along, or refuses

What

You can move a running session to the background with the left arrow key. Prompts you typed while Claude was busy wait in a queue. This release changes what happens to that queue when you move the session.

• Queued prompts are sorted into ones that can be carried over, ones that would be stranded, and ones being read at that moment.
• Prompts that can be carried over are written to a file, adopt.json.queued-prompts, for the background job and added back to the queue when the session resumes. Claude Code records if carried prompts get lost.
• Moving to the background can now be refused, with a message, when queued prompts cannot be moved.
• Naming the session automatically now happens after these checks. Before, Claude Code went straight to naming the session and starting the background job.
• A new environment variable, CLAUDE_BG_CARRIED_PROMPTS_SHA256, is now passed to or kept for background sessions alongside CLAUDE_BG_WORKSPACE_TRUSTED. One place removes it from the variables and another reads it. Its name suggests a SHA-256 fingerprint of the carried prompts.

Why

Prompts you typed just before moving a session to the background should no longer quietly disappear. The trade-off is that pressing the left arrow can now be refused when the queued prompts cannot be moved.