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
Planning Mode instructions may be too strict #4627
> "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
I'm experiencing the same issue. My agent config explicitly allows editing .md files:
permission:
edit:
"*.md": allowBut the hardcoded system-reminder "STRICTLY FORBIDDEN" still overrides my config.User-defined permissions should take precedence over built-in defaults.
Activity
joshuachendyb commentedon Jan 18, 2026
please close it ASAP。thk
duya25446 commentedon Feb 24, 2026
I'm experiencing the same issue. My agent config explicitly allows editing .md files:
github-actions commentedon Apr 26, 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.