Winri is an opinionated experimental window tiling manager for Windows that arranges your existing normal Win32 GUI application windows in a horizontally scrollable strip. It aims to give you keyboard-centric window management including positioning and sizing.
All winri actions are based on the Windows key, leaving other modifier keys free for application use. All native Windows shortcuts based on the Windows key are disabled. (Other modifiers can be used for winri actions but only when the Windows key is also used. For example, Ctrl+Win+Left is valid).
Winri is inspired by niri, a scrollable-tiling wayland compositor on linux.
Winri name is derived from "Win" (Windows) + "ri" (from "niri").
Only Windows 11 x64 is supported and tested right now. I do not plan to support Windows 10. I'm open to PR to support arm64 machines. PR to fix Windows 10 compatibility are welcome but must be tested on Windows 11 to prevent regression.
If winri prevents you from doing what you want in any way, open an issue to discuss about a solution to implement.
Status: Early prototype. Expect breaking changes until 1.0.0
- Horizontal scroll tiler with dynamic window widths
- Keyboard-centric navigation.
- One‑key fullscreen / half‑screen sizing
- Overview mode with live thumbnails
- Safe recovery: windows moved to visible viewport when exiting or on panic
Via Scoop (recommended):
scoop bucket add winri https://github.com/sub07/winri-bucket
scoop install winriWith cargo install (Rust toolchain required):
cargo install --git https://github.com/sub07/winriThen run winri from command line or create a shortcut to winri.exe.
Via Scoop:
scoop update winriPlease use the repo issue tracker to report bugs.
When reporting bugs, please include:
- Winri version (see
winri --version) - Windows version (see
winvercommand) - Steps to reproduce the issue
- Expected behavior
- Actual behavior
- Application logs located at
C:\Users\<user>\AppData\Roaming\winri\logs\winri.log. This is not required as it may contains sensitive data, but it will dramatically help debugging. - Screenshots or screen recordings if applicable
- Any other information you think may be relevant
Keybindings are not customizable yet.
In Tiler mode:
| Shortcut | Action |
|---|---|
| Win + Left / Right | Move focus to previous / next window |
| Win + Ctrl + Left / Right | Swap focused window with neighbor |
| Win + Q | Close focused window |
| Win + F | Resize focused window to fullscreen width |
| Win + C | Resize focused window to half of screen width |
| Win + Shift + Left / Right | Resize by increment (20 px by default) |
| Win + Up | Enter Overview mode |
| Win + Escape | Exit winri and restore windows |
In Overview mode:
| Input | Action |
|---|---|
| Click thumbnail | Focus original window & return to Tiler |
| Win + Down | Close overview |
Configuration is not implemented yet. It will include at least the following options:
- Keybindings
- Padding between windows
- Border color and thickness for thumbnails and focused window (border on focused window not yet implemented)
- Per-process modifiers (e.g. exclude certain apps from tiling)
You can check the config issue for more fields to come.
You can check the milestones to see planned features for upcoming releases.
Winri is open to contributions!
Before tackling an issue or submitting a PR, please check the issue tracker for existing discussions. Before submitting a PR, consider opening an issue first to discuss your ideas.
For your PR to be accepted, please ensure the following:
- Format code with
cargo fmt --all -- --check - Run this clippy command
cargo clippy --all-targets --all-features -- -D warnings -W clippy::pedantic -W clippy::nursery -W clippy::dbg_macro -A clippy::missing_errors_doc - Run tests with
cargo test --all-features - Run cargo-machete to ensure dependency hygiene:
cargo machete --with-metadata(install withcargo install cargo-machete)
Branch naming is flexible. I use feat/#issue_number but you can use whatever you prefer. Just give a meaningful name.
Winri aims to be built with stable Rust.
- Rust edition: 2024
- CI:
- check: fmt, clippy (check Contributing section), tests, cargo-machete
- build: Build winri.exe
- deploy: Create github release + Scoop bucket manifest update
- Dependencies:
windowscrate for Win32 APIrdevfor global input capturewinit+softbuffer(For custom windows)
Releases are automated via GitHub Actions on pushes to main.
Tagging is derived from GitHub releases automatically; manual tagging is not required for the standard flow.
Winri must run with administrative privileges to manipulate windows of elevated processes (like task manager). One can choose to run winri without admin rights, but then windows of elevated processes will be ignored.
Winri will never collect or transmit any user data. Bugs will be reported by users voluntarily.
Nonetheless, keep in mind that manipulating windows of other applications can have security implications, especially if those applications handle sensitive data.
- Single-monitor assumptions for now (multi-monitor works but not supported / tested)
- Hard-coded keybindings for now
- Some applications may not behave correctly (e.g. some UWP like windows calculator or settings)
See issue tracker for more.
Q: Will Winri work with all applications? A: Winri works with standard Win32 GUI applications. Some applications like UWP may not behave as expected.
Q: Can I customize keybindings? A: Not yet, but this feature is planned for future releases.
Q: Is there multi-monitor support? A: Not yet, but it is on the roadmap.
Experimental software manipulating arbitrary third-party windows. Use at your own risk; keep unsaved work backed up.
Microsoft Windows API can be inconsistent and buggy. If you encounter issues, please report them via the issue tracker, but understand that some issues may not be fixable due to limitations in the Windows API or specific application behaviors.