Feature request: allow steering a turn mid-flight without hard-aborting it

Problem

There's no middle ground between two interaction modes while Claude is working through a multi-tool-call turn:

1. Sending a message mid-turn (no interrupt) - it gets queued and only surfaces to Claude at the next tool-call boundary (after the current tool call finishes), not truly mid-execution. If Claude is mid-way through a single long-running tool call, the message just waits.
2. Hard-interrupting (Escape/stop button) - this aborts the entire in-flight turn, discarding whatever partial work was in progress, rather than pausing it.

The gap: there's no way to say "stop doing that specific thing, keep what's already done, and do X instead" mid-turn. You either wait for the next natural boundary to be heard, or you interrupt and lose in-progress work and have to re-explain context from scratch.

Concrete example

While Claude was mid-turn building out a set of related config/design knobs across a few files, I sent a correction ("this one value doesn't need to be exposed as a knob"). It only surfaced after the current tool call finished, by which point Claude had already gone further than intended. I then sent a follow-up ("actually, keep it, it's already built"), which meant Claude had to partially revert and then re-apply the same change across two separate tool-call boundaries instead of cleanly steering once. A true hard-interrupt in that moment would have been worse - it would have thrown away the whole in-progress multi-file change, not just redirected it.

Requested behavior

Some way to steer a turn without fully discarding it, e.g.:

• A visible "you have a pending message" indicator so the user knows it's queued rather than lost/ignored, and roughly when it'll be seen.
• And/or an interrupt mode that pauses the current tool call and lets the user inject guidance, with Claude resuming with that guidance folded in, rather than discarding the whole turn.

Environment

Claude Code CLI, Windows 11.