Context
The Windows port (x86_64, Windows 10 1809+ / Windows 11) is actively in progress: the codebase is cross-platform by policy (ConPTY via portable-pty, named-pipe IPC, DirectX rendering via GPUI), and it compiles — but it needs real-world eyes before the first signed .msi ships.
How to help
Build locally following the Windows build instructions and exercise:
- PTY basics: PowerShell + cmd sessions, resize behavior, Unicode output
- Fonts: system monospace detection, ligatures, CJK width
- IPC: the named pipe at
\\.\pipe\paneflow (system.ping should answer)
- Agent CLIs: launching Claude Code / Codex in panes, status detection
- Self-update harness:
paneflow --update-and-exit exit codes
Known limitations are catalogued in docs/WINDOWS.md.
Reporting
Use the Windows bug report template — it captures the Windows version and build info. Even a "everything works on my machine" report with your hardware is valuable signal.
Context
The Windows port (x86_64, Windows 10 1809+ / Windows 11) is actively in progress: the codebase is cross-platform by policy (ConPTY via
portable-pty, named-pipe IPC, DirectX rendering via GPUI), and it compiles — but it needs real-world eyes before the first signed.msiships.How to help
Build locally following the Windows build instructions and exercise:
\\.\pipe\paneflow(system.pingshould answer)paneflow --update-and-exitexit codesKnown limitations are catalogued in docs/WINDOWS.md.
Reporting
Use the Windows bug report template — it captures the Windows version and build info. Even a "everything works on my machine" report with your hardware is valuable signal.