Wiunix Tools · Windows · Beta
A Windows terminal that keeps RTL and LTR text understandable
Wiunix Terminal is an independent Windows desktop terminal focused on Persian, Arabic and mixed-direction workflows. It combines a familiar Windows Terminal foundation with Wiunix RTL behavior, PowerShell-friendly features and transparent offline distribution.

Designed for multilingual command-line work
Use familiar Windows shells and tools while keeping Persian, Arabic, commands, paths, numbers and URLs easier to follow together.
RTL and bidirectional text
Wiunix-specific behavior improves Persian and Arabic text mixed with left-to-right commands, paths, numbers and Latin output.
Tabs, panes and profiles
Organize PowerShell, Command Prompt, WSL, SSH and registered command-line profiles in a modern tabbed interface.
PowerShell-friendly workflow
Optional OSC 133 integration adds prompt and command boundaries without silently replacing an existing custom Enter binding.
Offline installation
The self-contained installer includes the required Microsoft.UI.Xaml dependency and verifies the bundled release before installation.
Portable mode
Extract and run without package registration, certificate installation or administrator access; settings remain with the app folder.
Open foundation
Derived from Microsoft Windows Terminal under the MIT License. Wiunix Terminal is independently developed and supported by Wiunix Ltd.
RTL + LTR together
Read Persian output without losing the command-line structure

A recognizable Windows experience
Modern terminal features with a clear Wiunix identity

Why the Store build declares full-trust desktop access
A terminal must start and manage local command-line processes. Windows identifies that normal desktop behavior with the restricted runFullTrust capability; it does not grant automatic administrator rights.
Required for terminal sessions
Wiunix Terminal uses desktop execution to create and manage user-requested PowerShell, Command Prompt, WSL, SSH and other local pseudoconsole sessions.
Sandbox alternatives are insufficient
A sandboxed app cannot launch and control arbitrary local desktop shells or provide the process lifecycle, working directories and ConPTY integration expected from a Windows terminal.
No automatic elevation
Sessions run as the signed-in user. Administrator access occurs only when the user deliberately starts an elevated process and approves Windows consent.
User-driven and locally scoped
The app installs no driver, privileged service, hidden remote controller or unrelated background command executor. Network-capable commands connect only when the user starts them.