[FEATURE] Allow for bash commands that do not register as a prompt

Status Open
Maintainer reply None cached
Activity 0 comments · opened Oct 14, 2026

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

Sometimes I am in a working directory with just claude open, but I need to call a single bash command to open vscode, compile a test, or some other one liner while claude is working and I do not need claude to do anything or know that I made the bash call. Right now I have to open another terminal to make the call or I have to reverse time in claude code so claude does not include my random bash command.

Proposed Solution

From the tui it would be nice to call something like !! mybash command and the double !! would tell the tui, "Do not send this bash command as a prompt for claude."

Alternative Solutions

Some other shorthand instead of !! for "claude code just run this and tell me the output do not make it a prompt" is fine.

Priority

Medium - Would be very helpful

Feature Category

Interactive mode (TUI)

Use Case Example

  1. I need to open up vscode or vim to edit a file !! code ./myfile.cpp
  2. I want to curl a file that I want to show claude !! curl ...
  3. Make sure a test is passing !! pytest ...

Really just any quick command to check something is working / fix something etc.

Additional Context

_No response_

View original on GitHub ↗