[FEATURE] Allow some commands to execute asynchronously

Open 💬 3 comments Opened Jan 18, 2026 by ANogin

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

Currently, if a command is entered while Claude is busy, it ignores it. But commands that do not involve model interactions can be easily executed right away - e.g. /exit, /rename, /usage can execute while the model is busy with something else.

Proposed Solution

Have the shell treat the main model execution similar to that of background agents - namely still be capable of interacting with the user for those interactions that do not require model to particupate

Alternative Solutions

_No response_

Priority

Low - Nice to have

Feature Category

Interactive mode (TUI)

Use Case Example

I am working on something. Model went into a long compaction cycle. I want to rename the current session to make it easier to fork it, and do not want to wait for compaction to end. I command /rename foo - would like the rename to take effect right away.

Additional Context

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗