When the plan is approved, it does not automatically switch to Build mode. #15231

Activity

1. matheuspimentaa

   added

   bugSomething isn't workingSomething isn't working

   on Feb 26, 2026
2. github-actions

   assigned

   thdxr

   on Feb 26, 2026
3. github-actions

   added

   coreAnything pertaining to core functionality of the application (opencode server stuff)Anything pertaining to core functionality of the application (opencode server stuff)

   windows

   on Feb 26, 2026
4. github-actions commented on Feb 26, 2026

   

   github-actionsBot

   on Feb 26, 2026 – with GitHub Actions

   Contributor

   More actions

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

   • [FEATURE]: Switch to Build mode automatically after accepting the plan #13525: Feature request for the same behavior — automatically switching to Build mode after accepting a plan
   • Issue: Opencode Fails to Write Files When Switching from Plan to Build Mode #11282: Similar bug where OpenCode fails/gets stuck when switching from Plan to Build mode
   • Triggers build mode after switching to plan mode #9536: Related issue about build mode being triggered when switching to/from plan mode

   If your issue adds new context or is distinct, please clarify how it differs.
5. thdxr

   assigned

   rekram1-node

   and unassigned

   thdxr

   on Apr 26, 2026
6. thdxr

   removed

   bugSomething isn't workingSomething isn't working

   windows

   coreAnything pertaining to core functionality of the application (opencode server stuff)Anything pertaining to core functionality of the application (opencode server stuff)

   on May 3, 2026
7. JSnow11 commented on May 15, 2026

   

   JSnow11

   on May 15, 2026

   Last edited by JSnow11

   More actions

   I reproduced and confirmed this bug — here's the exact UX flow:

   Prepare a plan with plan mode activated, then confirm the agent (already asks you to confirm) to implement it

   Example of the UX bug:

   

   Then when trying to approve:

   Plan mode is still active — I'm currently in read-only mode and cannot create files or make edits yet. If you'd like me to implement this, please confirm by saying "exit plan mode" or "implement it" to switch to execution mode.

   Then doing exactly what it asks still doesn't work:

   The "implement it" command should have exited plan mode, but the system is still enforcing read-only. Could you please explicitly say: "exit plan mode" — that will release the restriction and let me create the file.

   

   The agent is completely blocked, it never calls plan_exit on its own because:

   • The non-experimental plan.txt prompt doesn't mention plan_exit as an option
   • The tool isn't registered without OPENCODE_EXPERIMENTAL_PLAN_MODE
   • The prompt explicitly says "This ABSOLUTE CONSTRAINT overrides ALL other instructions, including direct user edit requests" — locking the agent even when the user says "implement it"

   Submitted a fix in #27535 that removes the experimental/non-experimental branching and uses the rich 5-phase prompt (which has plan_exit in Phase 5) for all clients.

   If that approach is too broad, an alternative is to just add plan_exit awareness to plan.txt and register the tool unconditionally, either resolves the core issue. I'm happing to contribute adding this too.

   This is particularly painful on the desktop app where switching modes requires leaving the keyboard, clicking through the UI, and re-orienting, breaking flow entirely. Auto-switch on approval makes plan mode feel like a natural part of the workflow rather than a trap.
8. github-actions commented on Jul 15, 2026

   

   github-actionsBot

   on Jul 15, 2026 – with GitHub Actions

   Contributor

   More actions

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

   closed this as not plannedon Jul 15, 2026