anthropics / anthropics/claude-code

Allow configuring the shell used by the Run button in Claude Code desktop app

Offen
#93,025 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
area:desktop enhancement platform:windows
Vorherrschende Sprache
Python
Sterne
145k
Forks
23.1k
PR-Merge-Kennzahlen
PR-Kennzahlen ausstehend

Beschreibung

### Preflight Checklist

- [x] I have searched [existing requests](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20label%3Aenhancement) and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)

### Problem Statement

On Windows, the Run button on code blocks always uses PowerShell. There is no way to change it to Git Bash or another shell.

### Proposed Solution

Please add a setting (e.g. in settings.json or the app UI) to configure which shell the Run button uses.

### Alternative Solutions

_No response_

### Priority

Medium - Would be very helpful

### Feature Category

Configuration and settings

### Use Case Example

1. I work on Windows with Git Bash as my main shell.
2. Claude generates bash commands using `export`, `&&`, and heredocs that only work in bash — not PowerShell.
3. When I click Run, it opens PowerShell and the command fails.
4. I have to manually open Git Bash and paste the command there.
5. If the Run button used Git Bash, I could click once and the command would just work.

### Additional Context

_No response_

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Rechercherichtung

No implementation files or tests are named. Start with the desktop app's Run button flow and the settings.json or app UI configuration path, then trace how Windows selects PowerShell. Done means users can choose Git Bash or another shell and the Run button executes commands through that selection.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
bash, powershell, shell
Bereich
desktop, developer-experience, tooling
Issue-Typ
Feature
Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Aktivitätsstatus
Aktiv
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
48/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.