mrkeyoor.com_
Fri 16 Oct 18:51 UTC
Dev Toolsevaluationupdated 14 Oct 2026

phantomat review

Phantomat is a Hyprland plugin that places desktop windows on an endless, zoomable canvas. It adds title search and spatial navigation so you can find an application without remembering its workspace.

+3 / 1dstars / 7d
Verdict

Our Phantomat install failed after 4 seconds because CMake 3.25.1 did not meet its 3.27 minimum. Give it a trial only if a shared floating canvas is worth maintaining a Hyprland plugin and checking your own desktop workflows. The open drag-and-drop report makes it a difficult recommendation for a work desktop that must stay predictable.

We ran it

Lab card: what happened when we ran phantomatScreenshot of phantomat (github.com/kaolti/phantomat)
Install✗ · 4s
Build—
Repo80 files~23,027 lines of source · 1.1 MB · 0 CI workflows · tests dir

Answers from our run

Does phantomat build from source?

The dependency install failed, and the project has no separate build step. We cloned commit a1e8a08 into a clean Debian container with 3 CPUs and no project-specific setup.

Who should not use phantomat?

Developers expecting the supplied Debian CMake environment to work unchanged: our install stopped because 3.25.1 was below the required 3.27.

What are the alternatives to phantomat?

ScrollOverview, niri. Our Phantomat install failed after 4 seconds because CMake 3.

Setup2/5CMake version blocked our install; Hyprland needs matching headers
Docs4/5Clear navigation and rollback guidance; CMake minimum omitted
Community3/5October 8 push and active desktop-interaction reports
Maturity2/5Narrow daily-use evidence; open drag-and-drop issue

Who it’s for

Hyprland users who prefer freely positioned windows and a searchable spatial desktop.
Omarchy users prepared to rebuild a compositor plugin after Hyprland updates.
Desktop experimenters who can inspect configuration changes and check their own application workflows.

Who it’s NOT for

Developers expecting the supplied Debian CMake environment to work unchanged: our install stopped because 3.25.1 was below the required 3.27.
Users dependent on ordinary workspace and tiling shortcuts: the README disables those actions on the floating canvas.
People who need dependable file and browser-tab dragging without local checks: issue 18 reports broken canvas dragging and its proposed fix remains open.
Users expecting broad graphics-stack validation: the README names one daily-use setup and says other setups are less tested.

Setup reality

Our sandbox install of commit a1e8a08 failed with exit 1 after 4 seconds. The log says CMake 3.27 or higher is required, but our environment ran 3.25.1. Configuration stopped; there is no successful build or test result from that attempt.

The documented route needs Hyprland 0.56 or newer with Lua configuration, GCC 15 or newer, and matching development files. It targets Arch or Omarchy and does not name a hosted service or API credential. Our harness used CMake; the desktop installer follows its own build route.

The installer backs up and edits your Hyprland configuration and loads the plugin. Hyprland upgrades require a rebuild, and preserved settings need manual comparison to receive newly added keys. The README's known daily-use configuration is narrower than its application-support claims.

Phantomat replaces workspace navigation with a shared canvas

Press the overview shortcut and Phantomat's documented interface pulls your windows into a searchable, zoomed-out canvas. Typing part of an application name takes you toward a matching window. This Hyprland plugin changes how you organize a desktop: windows occupy positions on an endless plane, and adjacent monitors show neighboring parts of it. The attraction is being able to locate work spatially without first remembering which workspace contains it.

Our checkout was 1.1 MB across 80 files, with roughly 23,027 source lines. That small download conceals a substantial change to everyday behavior. The README says ordinary workspace and tiling shortcuts do nothing while the canvas is active, because its windows float. Someone who relies on tiled layouts should treat that as the central tradeoff. A searchable overview is appealing, but adopting this one means deciding whether you want its desktop model too.

What happened when we ran it

Our run failed the install step after 4 seconds at commit a1e8a08. CMake required version 3.27 or newer, while the container supplied 3.25.1. The October 13, 2026 sandbox had 3 CPUs and 8 GB of RAM, used the lab-cpp:1 image, and ran without secrets or elevated privileges. The log ended with CMake reporting an incomplete configuration. Its repeated error messages identify a tool-version mismatch, not a rendering defect.

The lab found 0 CI workflow files, no Dockerfile, and a tests directory. We have no successful build or test result from that attempt. Raising the CMake version would address the reported configuration blocker, but the log does not establish what would happen next. Our harness followed a CMake path; the README's desktop installer uses its own build route. We cannot turn this failed sandbox step into a claim that the documented installer always fails.

A newer CMake is only the first prerequisite

The README requires a current Hyprland installation with Lua configuration, a recent GCC, and Hyprland development files. Its package command targets Arch or Omarchy. This is a plugin loaded into a running Linux compositor, so a generic headless Debian environment is a poor stand-in for an interactive desktop. No hosted account or API credential is part of the documented local route, but the graphical session and matching development files are.

The CMake 3.27 requirement appears at the start of CMakeLists.txt, yet the README's prerequisite paragraph doesn't name that minimum. Our CMake 3.25.1 environment stopped there. Separately, the installer checks the compiler and development packages, compares running Hyprland against installed headers, and modifies the Lua configuration after backing it up. Review those changes before loading the plugin into a desktop you depend on.

Hyprland updates create a recurring rebuild obligation

Phantomat hooks into compositor internals, and the README explicitly warns that a Hyprland update can break it until the plugin is updated too. Rebuilding after an update is part of owning this setup. The documented installer keeps your settings, which helps preserve preferences but leaves newly added settings absent until you compare them against the example configuration. A routine desktop upgrade therefore brings a plugin compatibility check and potentially some configuration maintenance.

The 80-file checkout includes an uninstall script, and the README says removal returns windows to the normal layout while retaining preferences unless you request a purge. That gives an experiment a documented exit. It doesn't establish recovery from every possible compositor failure, which we didn't exercise. Keep an accessible copy of your configuration and judge the plugin on the applications you use, especially where fullscreen behavior, menus, and monitor boundaries affect your work.

Drag-and-drop has an open report and an open fix

Issue 18 reports that file drops between Nautilus and Vivaldi fail in canvas mode, and browser-tab drags move the camera unexpectedly. The report identifies a different main-branch commit from our sandbox checkout. Its author says both actions work with Phantomat disabled. That's a relevant user report about this canvas implementation, although it is not a result we reproduced or evidence that every configuration behaves the same way.

Our 4-second failure occurred before any desktop interaction, so it says nothing about that report. Pull request 19 proposes canvas-aware drag targeting and changes to camera following; it remained open when checked. Its description also retains a limitation around placing a window created by tearing out a tab. If dragging files or browser tabs is central to your day, verify the merged code and those actions before making Phantomat your default desktop.

The documented daily-use setup is narrow

The author names daily use on Omarchy with Hyprland and NVIDIA graphics across a pair of monitors, then says other configurations are less tested. That's useful candor. The README describes Wayland and X11 application support, Wine and Proton games, persistent window positions, and a live visual tuner. These are project claims rather than independently measured compatibility results. Our review can't endorse their behavior across different graphics drivers, display scaling, or application combinations.

GitHub listed 219 stars and 13 open issues and PRs on October 14, 2026. The last push was October 8, and the drag-and-drop report and proposed fix were active that day. No latest release was returned. The push and issue activity support calling this a maintained experiment. The 0 CI workflows found by our lab and the unsuccessful setup leave us without automated release evidence to recommend it as a low-maintenance default.

Choose ScrollOverview for an overview, niri for scrolling tiles

ScrollOverview, Phantomat's upstream project, supplies a Hyprland overview without asking you to adopt this particular shared-canvas workflow. niri is a separate Wayland compositor organized around scrollable columns and dynamic workspaces, with independent window strips per monitor. Choose according to the navigation model you want. Phantomat earns a trial if floating windows across a spatial canvas solve your actual organization problem, and you can accept plugin rebuilds. Try your usual file-drop and browser-tab actions before moving the rest of your desktop onto it.

Alternatives

ProjectWhat it isPick it when
ScrollOverviewA Hyprland overview plugin that Phantomat originally forked.pick this instead when you want a workspace overview rather than Phantomat's shared floating canvas.
niri gh↗A Wayland compositor with scrollable tiling columns and dynamic workspaces.pick this instead when scrolling tiles and separate monitor strips suit you better than free canvas placement.

What people are saying

  1. [velocity-scout] kaolti/phantomat

Sources

  1. Phantomat requirements and navigation model
  2. CMake minimum requirement
  3. Desktop installer and configuration checks
  4. Canvas drag-and-drop report
  5. Proposed canvas drag-and-drop fix
  6. ScrollOverview README
  7. niri README

More dev tools reviews

compose-samples · librepods · sqlmap · coucou · world-execute-me-dsh-pv · mcp-extensions · the whole board →