Feature Request: Support for Native Windows (Remove tmux dependency for Windows developers)

[wangbaiyu888]

Is your feature request related to a problem? Please describe.

Yes. I am working on a Windows project that includes C# desktop applications (WPF/WinForms/.NET). Since C# desktop development deeply relies on native Windows APIs, compilers, and UI automation, it is impossible for me to fully build, test, and run the project inside WSL (Linux).

Currently, bmad-loop requires tmux and only runs inside Linux/macOS or WSL, which breaks the development workflow for native Windows/C# developers like me.

Describe the solution you'd like

According to the documentation:

"a native-Windows backend slots in as new files + a registration line each, with no engine edits — see Porting bmad-loop to a new OS. Native Windows is not yet shipped."

Since the architecture for native Windows support is already designed and reserved, I would like to request shipping the Native Windows backend as soon as possible. Replacing the tmux dependency with a Windows-native terminal multiplexer or alternative process manager would be a huge lifesaver.

Describe alternatives you've considered

I tried using WSL, but as mentioned, WSL cannot render or correctly handle Windows desktop UI application compilation and testing, so it is a dead end for my specific tech stack.

Additional context

• My Environment: Windows 11, PowerShell, Python 3.11+
• My Stack: C# Desktop App (.NET / WPF)
• Thank you for creating this amazing tool! Having native Windows support would allow a whole community of Windows/.NET developers to fully leverage bmad-loop.

[dracic]

Duplicate of #58 . We are even working in "two lanes", psmux and tmux-windows support, and probably herdr soon.