Answers not saving in one session

[LeBohdan]

What happened?

I've selected many times, but it ask me again and again in one session:
2. Always allow in this project [Bash(yarn *)]

The same for any other question.

What did you expect to happen?

One answer, no questions anymore.

Client information

Client Information

Qwen Code 0.13.0 (aebe889)
Runtime Node.js v22.20.0 / npm 10.9.3
OS linux x64 (6.17.0-19-generic)

Login information

No response

Anything else we need to know?

No response

[sergehuber]

I have the same problem whether I choose project or user. I checked the settings.json files are getting updated with the settings (permissions) but for some strange reason they are not used even after restarting qwen code. I am also using 0.13.0 that just introduce this feature.

[LaZzyMan]

I have the same problem whether I choose project or user. I checked the settings.json files are getting updated with the settings (permissions) but for some strange reason they are not used even after restarting qwen code. I am also using 0.13.0 that just introduce this feature.

@sergehuber @LeBohdan Could you please check if the newly added configuration when running /permissions in qwencode appears in the list?

[Shisouka]

I have same problem with Qwen Code Companion 0.13.0 in my VS Code IDE

[sergehuber]

Here is my project .qwen/settings.json file :
{ "permissions": { "allow": [ "Bash(cargo test)" ] }, "$version": 3 }
here is my user-wide ~/.qwen/settings.json file:
{ "modelProviders": { "openai": [ { "id": "qwen-3.5-256k", "name": "Qwen3.5 256k", "envKey": "LLAMACPP_API_KEY", "baseUrl": "http://localhost:8080/v1", "generationConfig": { "timeout": 300000, "maxRetries": 1, "contextWindowSize": 262000, "samplingParams": { "temperature": 0.7, "top_p": 0.95, "max_tokens": 65536 } } }, { "id": "qwen-3.5-128k", "name": "Qwen3.5 128k", "envKey": "LLAMACPP_API_KEY", "baseUrl": "http://localhost:8080/v1", "generationConfig": { "timeout": 300000, "maxRetries": 1, "contextWindowSize": 128000, "samplingParams": { "temperature": 0.6, "top_p": 0.95, "max_tokens": 65536 } } } ] }, "security": { "auth": { "selectedType": "openai" } }, "model": { "name": "qwen-3.5-128k" }, "$version": 3, "permissions": { "allow": [ "Bash(cargo test)", "Bash(cargo check)", "Bash(cargo build *)", "Bash(cargo clippy *)", "Bash(git add *)", "Bash(git commit *)", "Bash(cargo test *)", "Bash(cargo fmt *)", "Bash(cargo fmt)", "Bash(cargo install *)" ] } }

And here are the /permissions just after starting a qwen 0.13.0 new instance:
`> /permissions
Permissions: Allow Ask Deny Workspace (←/→ or tab to cycle)

Qwen Code won't ask before using allowed tools.
╭──────────────────────────────────────────────────────────╮
│ > Search… │
╰──────────────────────────────────────────────────────────╯

› 1. Add a new rule…
2. Bash(cargo test)
3. Bash(cargo check)
4. Bash(cargo build *)
5. Bash(cargo clippy *)
6. Bash(git add *)
7. Bash(git commit *)
8. Bash(cargo test *)
9. Bash(cargo fmt *)
10. Bash(cargo fmt)
11. Bash(cargo install *)
and if I resume a previous session here are the permissions now:> /permissions
Permissions: Allow Ask Deny Workspace (←/→ or tab to cycle)

Qwen Code won't ask before using allowed tools.
╭──────────────────────────────────────────────────────────╮
│ > Search… │
╰──────────────────────────────────────────────────────────╯

› 1. Add a new rule…
2. Bash(cargo test)
3. Bash(cargo check)
4. Bash(cargo build *)
5. Bash(cargo clippy *)
6. Bash(git add *)
7. Bash(git commit *)
8. Bash(cargo test *)
9. Bash(cargo fmt *)
10. Bash(cargo fmt)
11. Bash(cargo install *)

However if I ask something like this:> Could you rebuild the project and run the tests

✦ The user wants me to rebuild the project and run tests. Let me do a clean rebuild to verify everything
compiles correctly.

╭─────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ ? Shell cd /home/loom/projects/sergehuber/local-ai/llamamon && cargo clean && cargo build --rel… ← │
│ │
│ cd /home/loom/projects/sergehuber/local-ai/llamamon && cargo clean && cargo build --release 2>& │
│ tail -20 │
│ │
│ Allow execution of: 'cargo'? │
│ │
│ › 1. Yes, allow once │
│ 2. Always allow in this project [Bash(cargo clean), Bash(cargo build *)] │
│ 3. Always allow for this user [Bash(cargo clean), Bash(cargo build *)] │
│ 4. No, suggest changes (esc) │
│ │
╰─────────────────────────────────────────────────────────────────────────────────────────────────────╯
✦ Build succeeded. Now let me run all tests.

╭─────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ ? Shell cd /home/loom/projects/sergehuber/local-ai/llamamon && cargo test --release 2>&1 | tail… ← │
│ │
│ cd /home/loom/projects/sergehuber/local-ai/llamamon && cargo test --release 2>&1 | tail -30 │
│ │
│ Allow execution of: 'cargo'? │
│ │
│ › 1. Yes, allow once │
│ 2. Always allow in this project [Bash(cargo test *)] │
│ 3. Always allow for this user [Bash(cargo test *)] │
│ 4. No, suggest changes (esc) │
│ │
╰─────────────────────────────────────────────────────────────────────────────────────────────────────╯
`

Could it be due the different allow execution of 'cargo' instead of 'cargo test*' ? So maybe a problem in the comparison of what is allowed and what is detected ? Should we have, in the second example : Allow execution of: 'cargo test' instead ? (and in the case where the permissions are already given of course we wouldn't prompt at all but execute instead)

[LeBohdan]

@sergehuber @LeBohdan Could you please check if the newly added configuration when running /permissions in qwencode appears in the list?

Yes. It's in list. Just approved (again) Bash(git show *):

/permissions

     1. Add a new rule…
     2. Bash(timeout *)
     3. Bash(tee *)
     4. Bash(find *)
  ›  5. Bash(git show *)
     6. Bash(grep *)
     7. Bash(curl *)
     8. Bash(yarn *)
     9. Bash(./build.sh)
    10. Bash(git *)
    11. Bash(head *)
    12. Bash(ls *)
    13. Bash(git log *)
    14. Bash(cat *)
    15. Bash(mv *)

[abbasnaqdi]

+1