[FEATURE] Add option to disable 'Contains backslash-escaped whitespace' warning

Open 💬 9 comments Opened Mar 18, 2026 by TyreReviews

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

When running Claude code in a WSL environment on Windows, if the directory name has a space in it, it breaks all agentic workflows because it constantly asks for confirmation of proceeding for Contains backslash-escaped whitespace when running even the simplest shell command, such as ls.

Proposed Solution

Add a configuration option to allow shell commands with backslash escape whitespace.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

Configuration and settings

Use Case Example

❯ /init The test environment is being served at the following URL. http://localhost:8084 The MySQL database credentials are in a config file, one directory up, and you can query MySQL directly

● Running 3 Explore agents… (ctrl+o to expand) ├─ Explore codebase structure · 7 tool uses · 16.5k tokens
│ ⎿ Searching for 2 patterns, reading 5 files…
├─ Explore backend and API · 2 tool uses · 14.7k tokens
│ ⎿ Searching for 1 pattern, reading 1 file…
└─ Explore PWA frontend code · 25 tool uses · 61.2k tokens
⎿ Done

───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── Bash command
ls -la /mnt/g/My\ Drive/Websites/tyrereviews.com/Site/tyre.info/testing/
Run shell command

Contains backslash-escaped whitespace
Do you want to proceed?
❯ 1. Yes

  1. No

Additional Context

_No response_

View original on GitHub ↗

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