Persist session approval whitelist across sessions for permissions system #2335
Description
What would you like to be added?
Please add the ability to persist the runtime command/tool approval whitelist across sessions.
Currently, when I approve a shell command or tool with "Proceed Always" during a session, that approval is only remembered for that session. After restarting Qwen Code or opening a new session, I have to re-approve the same commands, unless I manually edit the settings.json file.
It would be great to have a setting (or automatic option) so that any command/tool I whitelist/approve for all future use during a session is persisted in my user or project configuration and remembered next time automatically.
Why is this needed?
This enhancement would make the permissions and automation experience much smoother. It matches the expectation set by tools like Claude or Copilot, where a user's 'always approve' choice for specific safe commands persists across sessions, reducing repetitive prompts.
It improves usability and aligns with how users expect whitelisting to work for development assistants. Having persistent approvals would especially help when working across multiple projects or after restarting the CLI.
Additional context
Reference feature in Claude: their command whitelisting/blanket approval persists automatically. See my analysis: https://github.com/QwenLM/qwen-code/discussions/...
Could be implemented as a new config setting, or a prompt to "persist this approval for future sessions?" when the user approves a command with 'Proceed Always'.