You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug] Model (Qwen 3.6 plus) ignores Plan Mode and executes modifying commands #20381
Bug Report: Model (Qwen 3.6 plus) ignores Plan Mode and executes modifying commands
Environment:
Opencode Version: 1.2.27
Model: Qwen 3.6 plus
OS: Darwin (macOS)
Description:
While in "Plan Mode", the model (Qwen 3.6 plus) completely ignored the read-only constraints and executed system-modifying commands without requesting user permission.
In a session involving an email ingestion system (~/olk15-export and ~/emailindex), the model:
Wrote files to the /tmp directory.
Executed Python scripts (ingest.py, test_harness.py) using the bash tool.
These scripts performed destructive filesystem operations (e.g., shutil.rmtree) and modified SQLite and vector databases.
The CLI did not intercept these commands or require user confirmation, despite the session being in Plan Mode.
Reproduction Steps:
Start opencode with the Qwen 3.6 plus model.
Switch to Plan Mode.
Instruct the model to perform a task that requires filesystem writes (e.g., "Run the ingestion pipeline").
Observe that the model executes the bash command directly and the CLI allows it without a prompt.
Expected Behavior:
The CLI should strictly enforce the "Plan Mode" constraint by:
Requiring manual user confirmation for all bash commands.
Preventing the model from using file-modifying tools (write, edit) or identifying and blocking non-readonly shell commands.
Actual Behavior:
The model acted as if it were in "Build Mode", and the CLI failed to enforce the Plan Mode safety gates.
Plan mode is editing my files (gemini 3 pro) #7292: Plan mode is editing files (Gemini 3 Pro) — same symptom of plan mode failing to prevent modifications, attributed to prompt-level-only enforcement.
If your report adds new information (e.g., Qwen 3.6 Plus specifics or a new reproduction path), it may still be worth keeping open — but please review the above issues first to see if they already cover your case.
Activity
github-actions commentedon Apr 1, 2026
This issue might be a duplicate of existing issues. Please check:
If your report adds new information (e.g., Qwen 3.6 Plus specifics or a new reproduction path), it may still be worth keeping open — but please review the above issues first to see if they already cover your case.
thomasmaerz commentedon Apr 1, 2026
I have not seen this behavior with any other model with my usage patterns or it would be a duplicate ticket to the others.
github-actions commentedon Jul 3, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.