swaywm/sway

i3-compatible Wayland compositor

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 29 minutes ago
Added to GitGenius on September 3rd, 2026
Created on August 5th, 2015
Open Issues & Pull Requests: 1,384 (+0)
GitHub issues: Enabled
Number of forks: 1,296
Total Stargazers: 17,311 (+1)
Total Subscribers: 216 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

Sway is an i3-compatible Wayland compositor that brings the tiling window manager paradigm to Wayland-based systems.

Sway addresses the need for a modern display server alternative to X11 by implementing a Wayland compositor that maintains compatibility with i3 configuration and workflow. Users familiar with i3 can migrate directly by copying their existing configuration file, which the tool reads without modification. The compositor manages window tiling, keyboard-driven navigation, and workspace organization using the same command syntax and configuration format as i3, eliminating the learning curve for existing users while providing access to Wayland's improved security and architecture.

Sway suits developers and power users who prefer keyboard-centric window management and want to move to Wayland without abandoning their established i3 setup. It works well in minimal desktop environments where users value efficiency and configurability over graphical menus. The project explicitly positions itself as an i3 alternative for Wayland, making the choice straightforward for anyone already using i3 or seeking that particular workflow style on modern graphics infrastructure.

The project maintains active engagement with its user base, with nearly all reported issues originating from adopters in production use rather than internal development priorities. Maintainers respond to new issues and pull requests within a day, ensuring problems receive prompt attention.