What would you like to be added?
I would like to request support for a configurable plansDirectory setting in Qwen Code CLI, similar to what is available in Gemini CLI and Claude Code.
In particular, Gemini CLI supports custom plan directories and policies (see: https://geminicli.com/docs/cli/plan-mode/#custom-plan-directory-and-policies
), and Claude Code provides a plansDirectory option to define where plan files are stored (relative to the project root, e.g. "./plans").
A similar configuration in Qwen Code CLI would allow users to:
Define a custom directory for plan files
Keep plan outputs organized within the project
Align with existing workflows used in other AI coding CLIs
Why is this needed?
This feature is especially useful when working in Plan Mode with restricted write permissions.
By limiting write access only to a dedicated plans directory, users can:
Safely allow the CLI to generate and store plans without granting full project write access
Persist plans for later reuse or iteration
Maintain better control over file system changes during AI-assisted workflows
It also improves consistency for users who are already familiar with similar features in Gemini CLI and Claude Code, making adoption of Qwen Code CLI smoother.
Additional context
No response
What would you like to be added?
I would like to request support for a configurable plansDirectory setting in Qwen Code CLI, similar to what is available in Gemini CLI and Claude Code.
In particular, Gemini CLI supports custom plan directories and policies (see: https://geminicli.com/docs/cli/plan-mode/#custom-plan-directory-and-policies
), and Claude Code provides a plansDirectory option to define where plan files are stored (relative to the project root, e.g. "./plans").
A similar configuration in Qwen Code CLI would allow users to:
Define a custom directory for plan files
Keep plan outputs organized within the project
Align with existing workflows used in other AI coding CLIs
Why is this needed?
This feature is especially useful when working in Plan Mode with restricted write permissions.
By limiting write access only to a dedicated plans directory, users can:
Safely allow the CLI to generate and store plans without granting full project write access
Persist plans for later reuse or iteration
Maintain better control over file system changes during AI-assisted workflows
It also improves consistency for users who are already familiar with similar features in Gemini CLI and Claude Code, making adoption of Qwen Code CLI smoother.
Additional context
No response