What happened?
When using the Qwen Code CLI to perform any task, it consistently fails to reference or follow the instructions provided in the qwen.md file. However, when interacting with the CLI in a general conversational manner, it is able to explain and reference the contents of qwen.md correctly. This suggests that the model does not treat qwen.md as part of its task-specific memory or context.
What did you expect to happen?
What did you expect to happen? I expected Qwen Code CLI to use the qwen.md file as a source of guidance or reference during task execution, especially when the task is directly related to the instructions or information provided in that file.
Steps to reproduce:
Create a qwen.md file with clear task instructions.
Run a task using Qwen Code CLI that should rely on those instructions.
Observe that the CLI does not follow or mention the contents of qwen.md.
Ask the CLI about the same topic in a general conversation — it responds correctly using the qwen.md content.
Client information
- CLI Version: 0.0.9
- Git Commit: 600c58b
- Operating System: win32 v22.18.0
- Sandbox Environment: no sandbox
- Model Version: qwen3-coder-plus
- Memory Usage: 214.6 MB
Login information
Standard CLI login
Anything else we need to know?
This behavior limits the usefulness of qwen.md as a task-specific guide and may lead to confusion or incorrect task execution. It would be helpful if the CLI could treat qwen.md as part of its active memory during tasks.
What happened?
When using the Qwen Code CLI to perform any task, it consistently fails to reference or follow the instructions provided in the qwen.md file. However, when interacting with the CLI in a general conversational manner, it is able to explain and reference the contents of qwen.md correctly. This suggests that the model does not treat qwen.md as part of its task-specific memory or context.
What did you expect to happen?
What did you expect to happen? I expected Qwen Code CLI to use the qwen.md file as a source of guidance or reference during task execution, especially when the task is directly related to the instructions or information provided in that file.
Steps to reproduce:
Create a qwen.md file with clear task instructions.
Run a task using Qwen Code CLI that should rely on those instructions.
Observe that the CLI does not follow or mention the contents of qwen.md.
Ask the CLI about the same topic in a general conversation — it responds correctly using the qwen.md content.
Client information
Login information
Standard CLI login
Anything else we need to know?
This behavior limits the usefulness of qwen.md as a task-specific guide and may lead to confusion or incorrect task execution. It would be helpful if the CLI could treat qwen.md as part of its active memory during tasks.