Hyprland-inspired control for your terminals.
Drag panes into place, resize your splits, and move around from the keyboard. Boomux brings your terminals, AI agents, and Git context into one native workspace on Linux, with a largely untested macOS preview and persistent Shells behind every view.
Website · Install Desktop · Desktop guide · Development
Real Desktop recording in Tree layout, with fictional demo terminal content. Watch the videos for playback controls, or view the recording notes.
- Move naturally. Grab a pane by its heading. It follows your pointer, then settles into the layout where you drop it.
- Make room. Resize from pane edges, switch between tiled and floating panes, or expand one pane without losing its place.
- Stay on the keyboard. Tap Ctrl + Space to enter layout mode, or hold it for a quick adjustment. Navigate, rearrange, and resize without reaching for the mouse.
- Keep your work running. Minimize a pane or quit Desktop; its Shell keeps running. Come back to the same process.
- See when you’re needed. Follow supported coding-agent activity in the Agents tab and check repositories, worktrees, and available PR status in Git.
- Bring remote work closer. Connect over SSH and open a Remote Workspace. Its Shells stay on that machine; manage connections and updates in Remotes.
- Feel at home. A native Rust / GPUI-CE interface with Ghostty terminal decoding, plus Omarchy theme integration.
The panes live inside Boomux’s own window. Hyprland inspires the interaction, but is not required: Desktop runs on X11, Wayland, or macOS. It does not embed arbitrary desktop applications or replace your window manager.
Warning
macOS is a largely untested experimental preview. It has limited automated CI and smoke-test coverage, with very little real-world testing. Everyday use, hardware compatibility, and session reliability are not established. Expect bugs; use it for evaluation only, not important work. Inclusion in a regular release does not make the macOS build stable or production-ready.
Install Boomux Desktop, including its matching Boomux CLI:
curl --proto '=https' --tlsv1.2 -LsSf \
https://github.com/gardnmi/boomux/releases/latest/download/boomux-installer.sh | sh -s -- --desktopThis downloads and runs the official release installer. It verifies the
release-pinned package and checksum and installs without sudo. The same command
selects Linux x86_64 or Apple Silicon macOS 15+. On Mac, open the versioned app
in ~/Applications; see the Mac guide for
first launch and updates. macOS support is experimental, ad-hoc signed, and not
notarized. On Linux, it adds an application-menu entry. Review the installation contract
and release downloads.
On Linux, launch Boomux Desktop from your application menu, or run:
boomux-desktopThe launcher starts or reuses the Boomux service automatically. Command links
on Linux live in ~/.local/bin; add that directory to your PATH if your shell does not
already include it. Existing independent CLI installations are preserved.
The current Desktop bundle supports GNU/Linux x86_64, glibc 2.39+, an X11 or Wayland session, and a working Vulkan driver. Ubuntu 24.04+ and current Arch are the Linux runtime baseline. An experimental Desktop bundle supports Apple Silicon macOS 15+. Intel macOS, ARM64 Linux Desktop, Windows, and musl/Alpine Desktop bundles are not currently provided.
- Ubuntu/Debian runtime
8000
libraries:
libfontconfig1,libwayland-client0,libx11-6,libxcb1,libxcb-shape0,libxcb-xfixes0,libxkbcommon0,libxkbcommon-x11-0, andlibvulkan1, plus your GPU’s Vulkan driver (such asmesa-vulkan-driversfor supported Mesa GPUs). - Arch equivalents:
fontconfig,wayland,libx11,libxcb,libxkbcommon,libxkbcommon-x11,vulkan-icd-loader, and your GPU’s driver. - An absolute
XDG_RUNTIME_DIRfor the service.
On Linux, the installer checks glibc and required graphics libraries; it does not install system packages. Rust and Zig are only needed for source builds.
Note
Stable Desktop releases support the Linux platforms listed above. Shells persist when you close Desktop, but pane arrangements and window geometry are not yet saved. See current limitations for terminal features that remain incomplete.
- Use + to create a Workspace. Configure project folders in Settings to open projects quickly from the same menu.
- Open Shells for your editor, development server, or coding harness.
- Arrange your panes with the mouse or layout mode.
- Use Agents, Git, and Remotes in the lower sidebar for context without another terminal shuffle.
Choose Tree or Tabs in Settings. Tabs is the default; the recordings here use Tree layout.
| Control | Action |
|---|---|
| Tap Ctrl + Space | Toggle layout mode |
| Hold Ctrl + Space | Use layout mode temporarily |
| Arrow keys in layout mode | Focus a neighboring pane |
| Shift + Arrow keys in layout mode | Move a pane |
| Alt + Arrow keys in layout mode | Resize a split |
| F in layout mode | Expand the focused pane; press again to return |
| O in layout mode | Toggle a pane between tiled and floating |
| Escape | Leave layout mode |
| Drag a pane heading | Move the pane |
| Drag a pane edge | Resize |
| Ctrl + Alt + B | Show or hide the sidebar |
Resize demonstration · Keyboard demonstration · Full controls
Boomux bundles integrations for Claude Code, Codex, OpenCode, Pi, and Kiro CLI v3. The service prepares them automatically on startup, including on remote machines, and updates unchanged managed integrations with the bundled version.
Your customizations and uninstall choices are preserved. Already-running harnesses may need restarting to load changes; host-specific approvals such as Codex hook trust still apply. Boomux does not install the harness applications themselves or replace their sign-in process.
Integrations report lifecycle events; quiet terminal output or process exit
alone does not establish Agent completion.
See automatic integration management
for opt-outs, customization protection, and troubleshooting.
See Kiro v2 and v3 for engine support and notification
limits. Use kiro-cli normally; Boomux preserves its default engine and agent.
Automatic v2 lifecycle reporting is unavailable.
Connect a machine from Remotes. Boomux uses your OpenSSH configuration and asks before installing software remotely. Remote Workspaces have a distinct machine icon, and all their Shells run on that machine.
Expand a machine card to create a New workspace, Update Boomux, or manage the connection. Forget connection only removes the local registration; it does not uninstall software or stop remote processes. Remove machine & uninstall Boomux is a separate, confirmed operation.
See remote-machine behavior for identity verification, unavailable machines, and removal guarantees. “Node” remains the underlying protocol term; Desktop presents machines through Remotes.
| Action | What happens |
|---|---|
| Minimize a pane or quit Desktop | Its managed Shell keeps running. |
| Explicitly remove a Shell | Its run ends and the Shell is removed. |
| Remove a Workspace | Its managed Shells are terminated as removal is confirmed by their owners. |
| Compatible graceful service restart | Running processes and PTYs survive the handoff. |
| Stop the service | Every managed process is terminated. |
| Crash or reboot | Live processes and PTYs are lost; durable Shell definitions return pending. |
Persistence is not process survival across a reboot. Terminal-history persistence is opt-in, and pane arrangements and window geometry are not yet saved. See lifecycle and ownership and live PTY handoff.
Use the gear button for appearance, pane layout, notifications, project folders,
and configuration access. Desktop preferences are stored in
~/.config/boomux-desktop/settings.toml (respecting XDG_CONFIG_HOME).
The service has separate configuration; see the
configuration architecture.
Desktop offers updates for eligible official bundles. Downloads and restarts are user-initiated. After an update is prepared, choose Restart now or Later; compatible updates use graceful handoff to preserve running terminals. Older installations may need a one-time migration through their owning updater.
See Desktop updates and migration and uninstalling for ownership and data-preservation details.
Use the documentation guide to find the right user guide, developer reference, or protocol contract.
The included CLI supports automation and a terminal dashboard. Use
boomux --help for its current commands. For scripts, use only commands
advertised in data.json_commands by boomux capabilities --json, invoke them
with --json, and parse the boomux.cli/v1 envelope. Human-readable output
is not a compatibility contract.
- Desktop guide and limitations
- Product concepts and architecture
- CLI JSON contract and event stream
- Integration compatibility evidence
- Web dashboard and access boundaries
- Optional Omarchy companion
- Security policy
Shells run with their owner’s privileges; they are not containers. Web-terminal access is shell access, and remote observations never authorize offline writes. Daemon sockets and durable stores are restricted to the current user. Attachment startup environments are not persisted, and terminal-history persistence is opt-in. Harness integrations and optional Omarchy plugins run unsandboxed in their host processes; review their access accordingly.
See DEVELOPMENT.md for prerequisites, isolated builds, focused validation, and the contribution workflow.
MIT. See Third-Party Notices for embedded assets and dependency policy for license and advisory checks.