Opencode running in plan mode called a subagent to bypass edit permission #8852

Activity

1. github-actions

   assigned

   rekram1-node

   on Jan 16, 2026
2. github-actions commented on Jan 16, 2026

   

   github-actionsBot

   on Jan 16, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues. Please check:

   • [CRITICAL Security Issue/Bug] Plan mode restrictions bypassed when spawning sub-agents #6527: [Security Issue/Bug] Plan mode restrictions bypassed when spawning sub-agents - This is the most direct match with detailed documentation of the same vulnerability
   • [bug] Restrict which subagents a custom agent can spawn (built-in Plan mode can write files via sub agent) #4267: Restrict which subagents a custom agent can spawn (built-in Plan mode can write files via sub agent) - Previously identified and closed as the same issue
   • [Security Bug] Subagent permissions not enforced - configured restrictions ignored #7474: Subagent permissions not enforced - configured restrictions ignored - Shows the root cause of subagents bypassing parent permissions
   • Plan mode is editing my files (gemini 3 pro) #7292: Plan mode is editing my files - Plan mode making file modifications when it shouldn't
   • Files were modified even being under 'Plan Mode' #5475: Files were modified even being under 'Plan Mode' - Similar plan mode file editing issue
   • Plan Agent does modifications to files. #2709: Plan Agent does modifications to files - Plan agent making modifications despite restrictions
   • The model loops attempting to edit files in PLAN mode #3038: The model loops attempting to edit files in PLAN mode - Model repeatedly trying to edit in plan mode

   Feel free to ignore if none of these address your specific case.
3. github-actions commented on Mar 26, 2026

   

   github-actionsBot

   on Mar 26, 2026 – with GitHub Actions

   Contributor

   More actions

   To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.
4. github-actions

   closed this as completedon Mar 26, 2026