Permission options 2 and 3 not persisting in Windows 11 CMD (re-prompts every time)

[askadityapandey]

What happened?

When using Qwen Code in Windows 11 CMD, selecting:

• "Always allow in this project"
• "Always allow for this user"

does not persist the permission.

The tool continues to prompt:

Allow execution of: 'git'?

on every run, even after selecting options 2 or 3 multiple times.

---

Steps to reproduce

1. Open Windows 11 Command Prompt (CMD)
2. Run a command that triggers the permission prompt (e.g. git execution via Qwen Code)
3. Select:
   • Option 2: Always allow in this project
     OR
   • Option 3: Always allow for this user
4. Run the same command again

---

Actual behavior

The prompt appears every time, as if no permission was saved.

---

Additional context

• Happens consistently
• Feels like permission state is not being written or read properly on Windows CMD
• Might be related to config storage path or shell-specific behavior

What did you expect to happen?

---

Expected behavior

The permission should be saved, and the prompt should not appear again for the same command.

Client information

---

Environment

• OS: Windows 11
• Shell: CMD (not PowerShell, not WSL)

Login information

No response

Anything else we need to know?

No response

[freerainboxbox]

Fails on macOS too.

[LaZzyMan]

linked #2640

[askadityapandey]

linked #2640

from what i can tell, this looks like a slightly different root cause

• in my case (windows cmd), it was due to case-sensitive path comparisons so workspace settings weren’t loading properly
• in Answers not saving in one session #2640 (linux), permissions are getting written to settings.json but not actually applied, which feels more like a mismatch between stored rules and detected commands

so both hit permission persistence, but prob in diff parts of the logic

happy to align if there’s overlap or tweak the fix if needed