{"version":"2.1.290","anchor":"daemon-queued-prompts-slash-commands-and-non-prompt-input-n","canonical_anchor":"daemon-queued-prompts-slash-commands-and-non-prompt-input-n","heading":"Background sessions no longer queue slash commands while starting","tier":"notice","area":"Sessions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/daemon-queued-prompts-slash-commands-and-non-prompt-input-n","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Background sessions no longer queue slash commands while starting\n\nMessages sent to a starting background session are no longer queued if they are slash commands, and replies may return a new code\n\n**Unclear.** How `ENOREPLY` is shown to the user is unclear.\n\n**What**\n\nWhen you send something to a background session that is still starting, Claude Code holds it in a queue until the session is ready. This has changed:\n\n- Slash commands, and anything that is not a plain prompt, are no longer queued.\n\n- A reply to a session that is still starting may now return the code `ENOREPLY` instead of `ERESPAWNING`.\n\n- Restarting a session with no messages now tries to recover it first.\n\n**Why**\n\nThis changes what happens to messages you send to a background session while it is starting up.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}