A considered setup

Install in a few careful steps.

Omarchy Activities lives in your user configuration. It does not replace Hyprland, patch the compositor, or install a required Hyprland plugin.

Compatibility note — Current implementation tested on Omarchy 4.0.4-1 with Hyprland 0.56.2-2. Other versions should be treated as unverified until tested.

Requirements

Omarchy with its Quickshell shell, Hyprland with the Lua IPC API used by this release, Python 3, and a POSIX shell. The included installer uses Bash and Python 3. Normal navigation and visual organising require no Python packages. The interface follows Omarchy’s active foreground, background, and accent colors automatically.

Install from the project

Clone the public project from its ngit announcement, then run:

git clone nostr://npub1pktmatjk0l8vn3jhfuwxaasjd65kn4ye9sce3egup7k993f8fg2q5tpxa6/relay.ngit.dev/Omarchy-Activities
cd Omarchy-Activities
./install.sh
hyprctl reload
hyprctl configerrors

The installer backs up files it replaces under ~/.local/state/hypr-activities/install-backups/, keeps existing config symlinks intact, and only adds the activity bar entry if one is not already present. It preserves unrelated settings. Review your Omarchy keybinding list before reload: activity navigation intentionally replaces global workspace cycling and numbered-workspace shortcuts.

Use the board

Open the workspace switcher

Press Super+M. Up and down choose activities; left and right choose workspaces. Enter or click opens the selection.

Move a window

Press Super+Shift+M. Select a workspace in any activity. The window moves; your current workspace stays in focus.

Arrange your activities

Press Super+Ctrl+Alt+Space or click the activity name in the bar. Add or rename rows, label workspaces, preview windows, and drag windows to where they belong.

Back out safely

Use the backup corresponding to the installation time if you need to restore a replaced file. Remove the feature import and bar entry, then the installed helper scripts, feature modules, and plugin folder. Existing windows remain on their current workspaces. Full rollback guidance is in the repository’s organiser guide.