GNOME 3721 Published by

The release candidate for Tiling Shell v18.0 just dropped with full GNOME 50 compatibility and a long-awaited right-click activation hook. The maintainer flipped the standard update pipeline by pushing release candidates to GitHub first, forcing users to validate their specific GNOME versions and monitor setups before upstream publication. New additions include a workspace-wide untile shortcut, synchronized layout propagation across virtual desktops, and hard patches for lingering signal leaks and Alt-Tab race conditions. The extension will only migrate to extensions.gnome.org once enough community confirmations prove it does not tear up existing window management pipelines.



Tiling Shell v18.0 RC Brings GNOME 50 Support and a Right-Click Activation Key

The release candidate for Tiling Shell v18.0 just dropped, and the solo maintainer is flipping the standard update pipeline. The release candidate targets GNOME 50 compatibility, swaps the classic Super key drag trigger for a right mouse button activation, and adds a dedicated shortcut to clear tiled grids. The code is available on GitHub right now, but the testing workflow has shifted dramatically.

Screenshot_from_2026_06_23_07_19_28

The New Release Pipeline and Why It Matters

Testing across GNOME 42 through 50 has become a logistical bottleneck for a single developer. Features like drawing tablet support refuse to validate themselves on a standard desktop setup. The maintainer is pushing feature-complete builds to GitHub as release candidates first. Users download the extension zip, install it manually, and report exactly what happens on their hardware.

A simple confirmation of GNOME version, distribution, and monitor setup actually moves the needle. Empty bug reports just add noise to the repository. Confirmed stable builds on specific configurations tell the maintainer it is safe to push upstream. But the real shift here is the expectation. The community needs to treat this as a pre-release validation sprint rather than a polished storefront drop.

What Actually Changes in the Tiling Shell v18.0 RC

Anyone who has tried dragging windows across mismatched monitors will recognize why the right-click hook matters. The previous drag detection lag used to break the tiling animation every single time. The right mouse button activation key finally arrived after years of requests from Windows power users migrating to Linux. GNOME's event loop makes intercepting drag operations incredibly tedious.

The contributor egme wired the hook properly anyway. Tiling triggers when you drag a window with the right button instead of the classic keyboard combo. The window untile command also got its own dedicated shortcut now. Users can clear a workspace of tiled grids without manually dragging every box back to its original position. Layout changes can finally propagate across all virtual desktops with a single toggle, though it stays off by default to preserve sanity.

A newer option limits the synchronized raise-together behavior to just the active monitor. Alt-tab race conditions and lingering signal handlers got patched out. The broken Super key drag trigger from earlier builds got reattached. Signal disconnect ordering prevents memory leaks during workspace switching. And the translation packs finally caught up. albanobattistella handled Italian, alewicki95 pushed Polish, and ChrisLauinger77 updated German.

Release [Release Candidate] Tiling Shell v18.0 | GNOME 50 support, right mouse button as activation key, keybinding to untile all the windows, bug fixes and more

Grab the release candidate and share your testing results here! Release Strategy Update Starting with Tiling Shell v18.0, the release strategy is changing!

Release [Release Candidate] Tiling Shell v18.0 | GNOME 50 support, right mouse button as activation key, keybinding to untile all the windows, bug fixes and more ยท domferr/tilingshell

The release pipeline shift actually makes sense for a tool that touches every corner of the GNOME desktop. Waiting for upstream validation just slows down feature iteration. Download the candidate, break something, and report back with version numbers instead of vague success claims. The extensions gallery version will appear once the community confirms the build does not tear up your window management stack.