Cannot start git bash tab under Windows 11

[limber swift]

Keep getting this issue on my laptop:

bash-4.4$ command -p stty raw;HISTCONTROL=ignorespace;HISTIGNORE=" *";WARP_SESSION_ID="$(command -p date +%s)$RAND
OM";_hostname=$(command -pv hostname >/dev/null 2>&1 && command -p hostname 2>/dev/null || command -p uname -n);_u
ser=$(command -pv whoami >/dev/null 2>&1 && command -p whoami 2>/dev/null || echo $USER);if [[ "$OS" == Windows_NT
]]; then WARP_IN_MSYS2=true; else WARP_IN_MSYS2=false; fi;if [ "$WARP_IN_MSYS2" = true ]; then _msg="\e]9278;k;A;
InitShell\a\e]9278;k;B;session_id;$WARP_SESSION_ID\a\e]9278;k;B;shell;bash\a\e]9278;k;B;user;$_user\a\e]9278;k;B;h
ostname;$_hostname\a\e]9278;k;C\a"; else _msg=$(printf "{"hook": "InitShell", "value": {"session_id": $WAR
P_SESSION_ID, "shell": "bash", "user": "%s", "hostname": "%s"}}" "$_user" "$_hostname" | command -p od
-An -v -tx1 | command -p tr -d " \n"); fi;WARP_USING_WINDOWS_CON_PTY=true;if [ "$WARP_USING_WINDOWS_CON_PTY" = tr
ue ]; then if [ "$WARP_IN_MSYS2" = true ]; then printf "$_msg"; else printf '"'"'\e]9278;d;%s\x07'"'"' "$_msg"; fi
; else printf '"'"'\e\x50\x24\x64%s\x9c'"'"' "$_msg"; fi;unset _hostname _user _msg
stty: 'standard input': unable to perform all requested operations
bash-4.4$

Tried a number of workarounds from ChatGPT, but wasn't able to solve the issue and I'm not exectly sure if they were correct in first place.

However, I didn't have any issues on my PC, also Windows 11 - Warp with bash works out of the box.

[sullen cliff]

Hi @limber swift. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

---

It looks like Warp’s shell bootstrap is running, but Git Bash can’t switch the TTY into raw mode (stty error), so Warp’s integration doesn’t complete. On Windows, Warp only supports Bash when it’s Git Bash (MSYS2/MSYS), not plain MSYS2 bash, and there have been a few Git Bash launch quirks that were recently fixed.

Try these steps:

• Ensure you’re using Git Bash (git-bash.exe or the bundled bash.exe), not MSYS2 Bash. Warp does not support MSYS2 Bash directly (use Git Bash or WSL) (Using shells on Windows).
• Update Warp to the latest version; Git Bash startup issues have been fixed recently (“can’t use git bash.exe on win11”).
• In Warp, set the shell to the Git-provided bash:
  • Prefer the path Git for Windows installs, e.g. C:\Program Files\Git\bin\bash.exe (or git-bash.exe). Some paths under Scoop/portable installs had problems that were addressed in newer builds, so updating Warp helps here (same issue thread).
• If the tab hangs on “Starting bash …”, enable “Show initialization block” from the command palette to confirm the bootstrap runs, then retry after updating (init block tip).
• If you are inside WSL or a customized kernel/PTY environment, note that detection logic matters; using stock WSL2 kernels fixed related init issues for others (WSL detection fix context).

If after updating you still get stty errors and the session doesn’t Warpify, it may be an unsupported MSYS2 Bash or an environment-specific PTY limitation. In that case:

• Switch to WSL2 or PowerShell for best support; Git Bash should also work when properly detected (Windows shells support).
• As a quick check, try a different Git Bash installation (e.g., standard Git for Windows installer vs. Scoop) and point Warp to its bash.exe (git-bash path issues).

If none of the above resolves it, please share your Warp version and the exact bash path you configured, plus a screenshot of the initialization block output so we can correlate with the known Git Bash fixes (diagnosis pattern; init block).

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

@limber swift Kapa.ai is still learning and improving, please let me know how I did by reacting below.