3dee0634c1
/background (/bg, /btw) exists to start independent work while the current turn keeps running. Typed while the agent was busy it went into _pending_input like ordinary input, and process_loop is blocked inside self.chat() for the whole run, so the background task only started once the foreground turn had finished. That is the one moment it was not needed. /steer had the identical problem and was fixed the same way, by dispatching inline on the UI thread. The command's own CommandDef already declares busy_policy="dispatch"; the gateway honours that, the classic CLI never consulted it. The foreground turn is untouched: no interrupt, no steer, and ordinary non-slash input keeps following the configured busy-input behaviour.