anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 18:25:32 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

Planning Mode instructions may be too strict #3049

New Issue
Open
opened 2026-02-16 17:38:23 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 17:38:23 -05:00
Owner
Copy Link
Copy Source

Originally created by @jshield on GitHub (Nov 22, 2025).

Originally assigned to: @rekram1-node on GitHub.

Description

> "CRITICAL: Plan mode ACTIVE - you are in READ-ONLY phase. STRICTLY FORBIDDEN: ANY file edits, modifications, or system changes... Any modification attempt is a critical violation. ZERO exceptions."

Even providing source code analysis that could be used to perform file modifications violates this constraint. The reminder explicitly prohibits this, including "direct user requests."

certain models end up getting stuck in this loop, requiring significant prompt back tracking to figure out what triggered this specific interpretation, seems to be relating to questions around code refactoring, even after clarifying that the user will use those recommendations to make changes themselves.

might be better when in plan mode to just disable any tool calls that have side effects, and any unknown tools ask the user on a per call basis, then tell the model that they should only read files, permitting them to provide analysis, etc

as switching to build mode in order to do analysis work seems backwards

OpenCode version

No response

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

Originally created by @jshield on GitHub (Nov 22, 2025). Originally assigned to: @rekram1-node on GitHub. ### Description ``` > "CRITICAL: Plan mode ACTIVE - you are in READ-ONLY phase. STRICTLY FORBIDDEN: ANY file edits, modifications, or system changes... Any modification attempt is a critical violation. ZERO exceptions." Even providing source code analysis that could be used to perform file modifications violates this constraint. The reminder explicitly prohibits this, including "direct user requests." ``` certain models end up getting stuck in this loop, requiring significant prompt back tracking to figure out what triggered this specific interpretation, seems to be relating to questions around code refactoring, even after clarifying that the user will use those recommendations to make changes themselves. might be better when in plan mode to just disable any tool calls that have side effects, and any unknown tools ask the user on a per call basis, then tell the model that they should only read files, permitting them to provide analysis, etc as switching to build mode in order to do analysis work seems backwards ### OpenCode version _No response_ ### Steps to reproduce _No response_ ### Screenshot and/or share link _No response_ ### Operating System _No response_ ### Terminal _No response_
yindo added the bug label 2026-02-16 17:38:23 -05:00
yindo commented 2026-02-16 17:38:23 -05:00
Author
Owner
Copy Link
Copy Source

@joshuachendyb commented on GitHub (Jan 18, 2026):

please close it ASAP。thk

@joshuachendyb commented on GitHub (Jan 18, 2026): please close it ASAP。thk
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#3049
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?