Platform Support & Compatibility

Wardian is built to be a high-performance terminal environment, leveraging native OS capabilities where possible.

🏆 Windows (Native Support)

Windows is the primary development and testing platform for Wardian.

Implementation: Wardian uses portable-pty with native ConPTY support. This ensures a true, high-fidelity Windows terminal experience (supporting PowerShell 7, Git Bash, and CMD).
Nuance: On Windows, Wardian handles UNC path resolution for Gemini logs and session state navigation, preventing common "path not found" errors when working across drive letters.
Pi shell requirement: Install Git Bash or another Bash-compatible shell supported by Pi before launching Pi agents on Windows.
Install: Use winget install WardianApp.Wardian, or download Wardian_X.Y.Z_x64-setup.exe from the Releases page.
Recommended Tools: We recommend using the latest PowerShell 7 for agent operations.

Wardian is fully supported on macOS, with a focus on Apple Silicon (M-series) performance.

Implementation: Standard Unix PTY via portable-pty.
Status: Stable. All core features (Library management, Automations, Telemetry) are verified on macOS.
Install: Use brew install --cask wardian-app/tap/wardian, or download the Apple Silicon or Intel .dmg from the Releases page. Official releases built by the signed automation are Developer ID signed and Apple-notarized; copy the app to Applications and eject the DMG before launch so updates have a writable install location.
Visuals: Native traffic lights share Wardian's overlay titlebar; the green control zooms the app window instead of opening a separate full-screen Space, so the controls stay available in the app chrome.

Wardian is fully supported on Linux.

Implementation: Standard Unix PTY via portable-pty.
Status: Stable. Core features verified on Linux. Distribution-specific shell environments are handled via the runtime shell selection feature.
Packages: .AppImage (portable, chmod +x and run) and .deb (install via sudo apt install ./Wardian_*.deb) are available from the Releases page.

If a terminal appears frozen or fails to render:

Check PTY Lifecycle: If the agent's PTY dies, the status will turn Gray (Off). Use Start Session to re-initialize it.
Provider Logs: Inspect the raw provider output using the Dynamic Terminal Grid (1x1 or focused view) to identify any CLI-level errors (e.g., authentication failure).
Shell Compatibility: Ensure the default shell on your system is supported by the agent provider you are using.