[Feature]Windows version under active development

[HCYT]

Windows version in progress — compatibility testing
We’re actively validating Windows compatibility across terminals, paths, and UI settings.

Scope

• cmd
• PowerShell
• WSL
• Image file paths.
• Config file paths.
• Color, font, and UI settings.

Tasks

• cmd: launch, basic commands, exit behavior.
• PowerShell: launch, profile/script interactions, encoding.
• WSL: invocation from Windows shell, path bridging, environment.
• Image paths: spaces, Unicode, absolute vs. relative, network drives.
• Config paths: default location under %APPDATA%, override via env/flags, read/write permissions.
• Colors/fonts/UI: ANSI color support, truecolor, font fallback, high-DPI scaling, theme alignment.
• Error handling: clear messages for missing paths/permissions; log with actionable hints.
• Documentation: record known limitations and workarounds.

Acceptance Criteria

• Launches and runs basic workflows in cmd, PowerShell, and WSL without crashes.
• Correctly resolves and accesses image and config paths on Windows.
• Renders colors, fonts, and UI consistently with design guidelines.
• Known limitations documented; CI covers core regressions.

Feedback

If you have Windows-specific features you’d like to see, please comment with your use case and examples.

[melekbadreddine]

Excited for this! Do you have a rough ETA for the Windows/Linux release?

[HCYT]

Excited for this! Do you have a rough ETA for the Windows/Linux release?

Hi @melekbadreddine

Windows support is currently in testing, but the initial builds will likely be unsigned.

For Linux, it looks like it can be built directly, but I don’t yet have anyone helping me verify and test it, so there’s no timeline for a Linux release at the moment.