{"version":"2.1.286","anchor":"queued-prompt-flag-passed-into-user-input-processing","canonical_anchor":"queued-prompt-flag-passed-into-user-input-processing","heading":"Queued prompts are now marked as queued when Claude Code processes them","tier":"internal","area":"Message Queue","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/queued-prompt-flag-passed-into-user-input-processing","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Queued prompts are now marked as queued when Claude Code processes them\n\nClaude Code now records whether a prompt was queued when it starts processing it\n\n**Unclear.** What changes for a user when a prompt is marked as queued is not established.\n\n**What**\n\nYou can type a new prompt while Claude Code is still working, and it is held in a queue until Claude Code is ready. When Claude Code picks up a prompt to work on, it now records whether that prompt came from the queue. It also passes that information on when it runs the prompt.\n\n**Why**\n\nIn practice, Claude Code can now treat prompts that waited in the queue differently from ones you typed directly. That may change how queued prompts appear on screen.\n\n- Area: Message Queue\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}