/usage, /model and /config commands should work immediately even with a pending process

Summary

The /model and /config slash commands should be executable immediately, even when there is a pending/running process in the Claude Code harness. Currently, these commands are blocked until the pending process completes.

Expected Behavior

/model and /config are read/write operations on local settings — they do not interact with any running process or tool call. They should be immediately available at any time, including while:

• A tool call is in progress
• A background task is running
• The harness is waiting on a subprocess

Actual Behavior

When a process is pending in the harness, /model and /config commands are blocked (the status dialog is dismissed without taking effect, or the user must wait for the process to finish).

Why This Matters

These are lightweight configuration commands. Blocking them on unrelated process state creates unnecessary friction — for example, a user cannot switch models mid-session while a background sync or long-running tool is executing, even though the model change would only affect subsequent requests.

Suggested Fix

Treat /model and /config (and potentially other pure-settings commands) as "interrupt-safe" — execute them synchronously against local config without waiting for pending process state to clear.

🤖 Generated with Claude Code