The new interface cannot toggle between Build and Plan modes.

[aaakirito]

The new interface cannot toggle between Build and Plan modes.

[github-actions]

This issue does not follow our contributing guidelines.

What needs to be fixed:

• No issue template was used — the issue body is completely empty (only the title was filled in)
• A Bug Report template is required with a Description field explaining what is happening and how to reproduce it
• Please include system/environment information (OS, version, etc.)

Please edit this issue to address the above within 2 hours, or it will be automatically closed.

---

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

• Bug: Plan/Build mode toggle missing from chat UI after latest update #37070: Plan/Build mode toggle missing from chat UI after latest update
• [Bug] Desktop App v1.18.1 new layout hides agent (Plan/Build) switching UI #36997: Desktop App v1.18.1 new layout hides agent (Plan/Build) switching UI
• Desktop app on macOS 1.18.1: session history inaccessible, slash commands broken, Plan/Build toggle disappeared in new layout #37025: session history inaccessible, slash commands broken, Plan/Build toggle disappeared in new layout
• Stuck in Plan Mode - cannot switch to Build mode #37101: Stuck in Plan Mode - cannot switch to Build mode
• Cannot leave Plan mode #37988: Cannot leave Plan mode
• Build/Plan missing in 1.18.4 #38054: Build/Plan missing in 1.18.4

If you believe this was flagged incorrectly, please let a maintainer know.

[doesitmaterter]

I found a way around solution . Open up a new session from the top plus button or ctrl+t while having Settings -> General -> Scroll to the bottom -> Enable "Show Agent"

[onelpawarai]

https://github.com/onelpawarai/ZYRAXON-AI.git Please support my project."

[github-actions]

This issue has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window.

Feel free to open a new issue that follows our issue templates.

[jessejohnson]

This is such an unfortunate change. Most sensible workaround was to go back to the old UI @aaakirito