[BUG] Shift + Tab is not working in powershell on windows native

I am having the same problem

Sam issue on my setup which is the same as the one reported

same

I am having the same issue.

Same

@ant-kurt Please check out this bug when you have time. Thank you very much

i have the same question , please fixed it

I cannot cycle to Plan mode, but I asked Claude to "Make a plan first", and it worked, it provided me with a plan and asked me to proceed or keep planning like Plan mode.
I think this is the only workaround for now if you guys want to use Plan mode

I think Shift+Tab should be YOLO Mode not Plan Mode

Hey folks, can you share more details:

• Windows 10 or 11?
• Running in Windows Terminal?
• Running in an IDE?
• What happens when you press shift+tab?
• Does auto-accept edits (shift-tab once) toggle as well?

I'm able to enter plan mode on Win11 + Windows Terminal (outside of and within VS Code) - trying to get a repro on this one!

I'm using Windows 11 Pro

• I tried using the Windows Terminal both with Powershell and Command Prompt
• I tried Powershell and Command Prompt from VSCode

In all cases I see the default ? for shortcuts no matter how many times I smash Shift+Tab. I can uppercase letters using Shift so it seems to recognize it in the terminal. It's more difficult to see how it's interpreting the Tab key.

My Mac is perfectly responsive when I switch modes.

I'm using Windows 11 Pro I tried using the Windows Terminal both with Powershell and Command Prompt I tried Powershell and Command Prompt from VSCode In all cases I see the default ? for shortcuts no matter how many times I smash Shift+Tab. I can uppercase letters using Shift so it seems to recognize it in the terminal. It's more difficult to see how it's interpreting the Tab key.

Exactly the same for me. @ant-kurt You may also be interested in knowing that I have WSL 2 running and Claude is installed in WSL 2 as well as native windows. I also have Power Toys installed. But neither of these facts have interferred withe Claude working in WSL 2 with Shift + Tab.

Claude even works with powershell -> wsl -> claude.

@ant-kurt I am using W10. I use PowerShell mainly, but tried the usual Terminal as well. The issue persists.
When pressing shift + tab, simply nothing happens.

i find :mode code

Hey folks, can you share more details:大家好，能否分享更多细节： Windows 10 or 11?Windows 10或11？ Running in Windows Terminal?在Windows终端中运行？ Running in an IDE?在IDE中运行？ What happens when you press shift+tab?当你按下Shift+Tab时会发生什么？ * Does auto-accept edits (shift-tab once) toggle as well?自动接受编辑（shift-tab一次）是否也会切换？ I'm able to enter plan mode on Win11 + Windows Terminal (outside of and within VS Code) - trying to get a repro on this one!我能够在Win 11 + Windows终端上进入计划模式（在VS代码之外和之内）-试图在这一个上获得一个再现！

On Windows 11, using powershell or CMD shift+tab cannot be used to switch modes. Pressing this key combination has no effect and no response, whether in the IDE or not. Pressing the keys in auto-accept mode also has no response. I can switch modes normally in wsl2

Also getting this issue using CMD prompt on windows 11. Not in a IDE just native.

Hey folks, can you share more details: Windows 10 or 11? Running in Windows Terminal? Running in an IDE? What happens when you press shift+tab? * Does auto-accept edits (shift-tab once) toggle as well? I'm able to enter plan mode on Win11 + Windows Terminal (outside of and within VS Code) - trying to get a repro on this one!

I have also added a json file with my setup if that helps.
terminal_diagnostic_public.json

Windows 10 or 11?: Windows 11
Running in Windows Terminal: Yes
Running in an IDE: Yes
What happens when you press shift+tab: nothing at all in either.
Does auto-accept edits (shift-tab once) toggle as well: no there is no toggling at all in either scenario.

If anyone else want to get the setup data like I did here is the command line prompt:

get-system-info-safe-to-post-online.txt

Same issue W11, in Cursor IDE or Powershell same

• Windows 11 - 23H2 22631.5472, PowerShell 7.5.2
• Both terminal and VSCode
• What happens when you press shift+tab? nothing happens
• Does auto-accept edits (shift-tab once) toggle as well? No, nothing happens.

I think this bug is critical, we cannot use plan mode in windows.

Thanks

same here

I'm using Windows 11, both Windows Terminal and Powershell have the same issue.
Nothing happens when pressing Shift + Tab (Does not cycle into auto edit mode or planning mode).

I think it might be related to windows terminal binding the shift+tab to the path cycle.

Thanks for all the environment details - we're working on a fix for this and https://github.com/anthropics/claude-code/issues/3442.

As a workaround, you can start Claude like this: claude --permission-mode plan (see claude --help for more details).

Im using Windows 11 Pro with Powershell

I was having this issue but upgrading to the latest version of node (v24.x - specifically 24.4.0) has allowed me to use Shift+Tab. If you aren't using this version of node then give it a try.

@Ixe1 I believe this is due to https://github.com/nodejs/node/pull/58358 (in Node 24.2.0 and 22.17.0).

We're likely going to remap shift+tab to another chord that isn't modifiers-only - just for Windows users on other versions of Node. This was a fairly straightforward mitigation, we're working on addressing #3442 in tandem.

I was having this issue but upgrading to the latest version of node (v24.x - specifically 24.4.0) has allowed me to use Shift+Tab. If you aren't using this version of node then give it a try.

Thanks this worked for me. Had to reinstall Claude code after upgrading but may have been for other reasons.

did I wake up in the future are we're supposed to be using Node 24?

I updated to node 22.14.1 this morning and re-installed claude-code to it. Shift-tab didn't seem to be working. Now it seems to be working. I don't even remember re-starting my claude session, but maybe I'm brain-fading. Or.... is claude auto-updating, even while I'm using it? 😨

@Ixe1 I believe this is due to nodejs/node#58358 (in Node 24.2.0 and 22.17.0). We're likely going to remap shift+tab to another chord that isn't modifiers-only - just for Windows users on other versions of Node. This was a fairly straightforward mitigation, we're working on addressing #3442 in tandem.

When do you expect this update to be released?

I updated to node 22.14.1 this morning and re-installed claude-code to it. Shift-tab didn't seem to be working. Now it seems to be working. I don't even remember re-starting my claude session, but maybe I'm brain-fading. Or.... is claude auto-updating, even while I'm using it? 😨

I updated to node 24.4.1 and shift+tab worked now for Claude 1.0.53

@Ixe1 I believe this is due to nodejs/node#58358 (in Node 24.2.0 and 22.17.0). We're likely going to remap shift+tab to another chord that isn't modifiers-only - just for Windows users on other versions of Node. This was a fairly straightforward mitigation, we're working on addressing #3442 in tandem.

Can this be optional so it isn't an issue for people that use Claude on multiple platforms?

I was having this issue but upgrading to the latest version of node (v24.x - specifically 24.4.0) has allowed me to use Shift+Tab. If you aren't using this version of node then give it a try.

Working also for me. Thanks!

Adding here that the solution also for me, using Windows 10 and a powershell in Cursors, was just to update to the latest Node.js

Updating node fixed it for me as well.

In v1.0.54 we're going to re-map it to alt+m on Windows.

Can this be optional so it isn't an issue for people that use Claude on multiple platforms?

Can folks who feel strongly about this react to this post with a 👍 or 👎 on if they would like Claude Code to only remap for Node.js where >=22.17.0 <23.0.0 || >=24.2.0 is not satisfied?

👍 = "On Windows: newer versions of Node should use shift+tab, older versions of Node should use alt+m"
👎 = "I always want to use alt+m on Windows"
😕 = "I have a third proposal, which I'm commenting below!"

In v1.0.54 we're going to re-map it to alt+m on Windows. > Can this be optional so it isn't an issue for people that use Claude on multiple platforms? Can folks who feel strongly about this react to this post with a 👍 or 👎 on if they would like Claude Code to only remap for Node.js where >=22.17.0 <23.0.0 || >=24.2.0 is not satisfied? 👍 = "On Windows: newer versions of Node should use shift+tab, older versions of Node should use alt+m" 👎 = "I always want to use alt+m on Windows" 😕 = "I have a third proposal, which I'm commenting below!"

Add a settings so we can choose the keybinding ourselves

In v1.0.54 we're going to re-map it to alt+m on Windows. > Can this be optional so it isn't an issue for people that use Claude on multiple platforms? Can folks who feel strongly about this react to this post with a 👍 or 👎 on if they would like Claude Code to only remap for Node.js where >=22.17.0 <23.0.0 || >=24.2.0 is not satisfied? 👍 = "On Windows: newer versions of Node should use shift+tab, older versions of Node should use alt+m" 👎 = "I always want to use alt+m on Windows" 😕 = "I have a third proposal, which I'm commenting below!"

I haven't dug into the node issue, but assuming it's a bug fix that is unlikely to resurface, I'd consider checking the node version and if running on the affected range, then show a Claude startup message to inform the user of the issue and to upgrade node for the fix.

My order of preference:

1. startup message informing user to upgrade node if on affected version range (assuming it's a node bug that is fixed)
2. auto remap only if in node version range and on Windows
3. offer setting that defaults to shift+tab

Items 2 and 3 are pretty interchangeable and order likely depends on if you make the effort to make the chord customizable.

Edit: To be clear, it doesn't really make much difference what the chord is to me, may ask is to have a way to make it consistent on all platforms.

> In v1.0.54 we're going to re-map it to alt+m on Windows. > > Can this be optional so it isn't an issue for people that use Claude on multiple platforms? > > > Can folks who feel strongly about this react to this post with a 👍 or 👎 on if they would like Claude Code to only remap for Node.js where >=22.17.0 <23.0.0 || >=24.2.0 is not satisfied? > 👍 = "On Windows: newer versions of Node should use shift+tab, older versions of Node should use alt+m" 👎 = "I always want to use alt+m on Windows" 😕 = "I have a third proposal, which I'm commenting below!" Add a settings so we can choose the keybinding ourselves

Some generalised rebinding functionality would be nice so we could, for example, remap ctrl+z to "undo", since ctrl+z can't background claude on Windows, see: https://github.com/anthropics/claude-code/issues/3586.
So I could either workaround the crash by rebinding ctrl-z to nothing, or even better bind it to undo so claude works like my IDE.
There's other keys that are presenting issues to people to (shift+enter, esc, etc.)

Not saying it's worth building for this specific issue though - worth a new feature reqest?

v1.0.54 released a couple hours ago, with rebinding to alt+m for all Windows native installations. Based on the above poll, we may change this behavior in the future.

v1.0.54 released a couple hours ago, with rebinding to alt+m for all Windows native installations. Based on the above poll, we may change this behavior in the future.

I hope you do change it, I'm unsure about other users, but after upgrading to Claude v1.0.53 and node v24.4.1 it was working fine. Now I have a different keybinding on different machines.

Also, the poll is over 5:1 based on target users (people watching this issues)

<img width="1000" height="177" alt="Image" src="https://github.com/user-attachments/assets/4a5f4e39-4420-40dc-8877-d335e4c348c3" />

Thanks @ant-kurt 

Does ALT-M work for other's in VSCode/Cursor/etc when in the terminal? The terminal seems to capture ALT-anything when focused for me.

How can i change this to shift tab again?

Why can't it be both? So if you have current node js Shift Tab and ALT-M works and if on older node then use Alt M.

This is going to be confusing for anyone doing demos with 2 different workflows to explain. I was so happy when Shift Tab came back to life.

Also where is the information distribution for all Windows users about this change? I watch many channels and see nothing.

Warm regards,
Tony

On Fri, 18 Jul 2025 at 8:44 am, Jacob Hällgren < @.*** > wrote:

jacobhallgren left a comment (anthropics/claude-code#3368) ( https://github.com/anthropics/claude-code/issues/3368#issuecomment-3085733122 ) How can i change this to shift tab again? — Reply to this email directly, view it on GitHub ( https://github.com/anthropics/claude-code/issues/3368#issuecomment-3085733122 ) , or unsubscribe ( https://github.com/notifications/unsubscribe-auth/AASXK7IFGJ5DBDLUM3BFQID3JARNVAVCNFSM6AAAAACBLA77W6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTAOBVG4ZTGMJSGI ). You are receiving this because you commented. Message ID: <anthropics/claude-code/issues/3368/3085733122 @ github. com>

I’ve updated to the latest:

Node.js v24.4.1

Claude Code v1.0.55

But Shift + Tab still doesn’t toggle planning mode on Windows (PowerShell).
Alt + M works, but Shift + Tab still appears to be disabled, even though the Node version should no longer have the input issue.

Would be helpful if the shortcut could switch automatically based on Node version, or if users could configure their preferred keybinding (e.g., in .claude.json).

I see Alt+M can switch between Plan Mode and Auto Accept but it's better to split this two thing to two keybinds

Working after upgrading to Stable Node.js and v1.0.55

@PierrunoYT Is it working with tab or alt + m for you?

@PierrunoYT Is it working with tab or alt + m for you?

It's working only with alt + m which switch to plan mode or auto accepts on latest cc version

I was on Claude Code 1.0.55 and ran claude update and it "updated" to 1.0.53...

Niether alt+m nor shift+tab work in either version of CC (1.0.53 or 1.0.55). I'm using Powershell w/ npm version 11.4.2 and node version 22.16.0.

Based on the above poll, in the next few days we will release a version that implements: "On Windows: newer versions of Node should use shift+tab, older versions of Node should use alt+m".

Based on the above poll, in the next few days we will release a version that implements: "On Windows: newer versions of Node should use shift+tab, older versions of Node should use alt+m".

But why is the same keybind also used for plan mode?

> Based on the above poll, in the next few days we will release a version that implements: "On Windows: newer versions of Node should use shift+tab, older versions of Node should use alt+m". But why is the same keybind also used for plan mode?

Mode cycling (between standard mode, auto-accept edits, and plan mode) uses one keybind. We're not currently planning to split these into two different keybinds.

> > Based on the above poll, in the next few days we will release a version that implements: "On Windows: newer versions of Node should use shift+tab, older versions of Node should use alt+m". > > > But why is the same keybind also used for plan mode? Mode cycling (between standard mode, auto-accept edits, and plan mode) uses one keybind. We're not currently planning to split these into two different keybinds.

Why will old node use alt m?

> > > Based on the above poll, in the next few days we will release a version that implements: "On Windows: newer versions of Node should use shift+tab, older versions of Node should use alt+m". > > > > > > But why is the same keybind also used for plan mode? > > > Mode cycling (between standard mode, auto-accept edits, and plan mode) uses one keybind. We're not currently planning to split these into two different keybinds. Why will old node use alt m?

https://github.com/nodejs/node/pull/58358.

Just updated to 1.0.56 and the alt+m keybind is cycling through the modes.

same here

same here

download this https://nodejs.org/en/blog/release/v22.17.1 and update claude code

> same here download this https://nodejs.org/en/blog/release/v22.17.1 and update claude code

Which key combination will work with this?

@jacobhallgren ALT+M

@jacobhallgren ALT+M

I have npm v24.4.1

and @anthropic-ai/claude-code@1.0.56

should not shift + tab work for me then?

> @jacobhallgren ALT+M I have npm v24.4.1 and @anthropic-ai/claude-code@1.0.56 should not shift + tab work for me then?

Only for older nodes version I think?

> > @jacobhallgren ALT+M > > > I have npm v24.4.1 > and @anthropic-ai/claude-code@1.0.56 > should not shift + tab work for me then? Only for older nodes version I think?

but this quote?

"On Windows: newer versions of Node should use shift+tab, older versions of Node should use alt+m".

> > > @jacobhallgren ALT+M > > > > > > I have npm v24.4.1 > > and @anthropic-ai/claude-code@1.0.56 > > should not shift + tab work for me then? > > > Only for older nodes version I think? but this quote? "On Windows: newer versions of Node should use shift+tab, older versions of Node should use alt+m".

I think this was written the wrong way? @ant-kurt

Based on the above poll, in the next few days we will release a version that implements: "On Windows: newer versions of Node should use shift+tab, older versions of Node should use alt+m".

Thank you, this is greatly appreciated as a solution as I love/prefer using Shift Tab like the cool Mac kids do.

This new version stinks, I also notice the ability to do ctrl + v disappeared in version V1.0.56

Update in 1.0.57 shift tab works again, thanks!

@jacobhallgren It doesn't work on powershell. Installed globally with bun, v1.0.57, with IDE integration VSCode

Solution : If you're using Claude Code for VSCode, use "ALT + M".

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.