GitHub - paulsp94/omacosy: Pre-1.0. An omarchy-style desktop environment for macOS: tiling with a real Super key, dwindle layout, a themed status bar written for it, focus-follows-mouse, trackpad workspace swipes and a live workspace overview — ~157MB, six self-built Swift binaries, one repo. Built and tested on macOS 26 / Apple Silicon.

omakase + macOS + cosy. An omarchy-style setup for macOS: tiling window management with a real Super key and Hyprland's dwindle layout, a status bar built for it (bar, popups, sliders and screen dimming in one process), focus follows mouse, trackpad workspace swipes, a Mission-Control-style workspace overview with live previews, focused-window border rings, and one theme switch that covers everything down to the wallpaper. All of it installs from this one repo.

The whole environment idles at about 157MB of memory. Numbers per process in Memory use.

Most of it is five small signed Swift binaries built by the installer, because several of the existing tools are broken on macOS 26. The details are under What's inside.

Built for macOS 26 (Tahoe) on one desk: a MacBook Pro plus one external display. It tries to generalize (display roles instead of hardware names, per-display notch detection), but so far it has only run on this machine. The permission setup is real work. Issues and PRs welcome; support promises are not made.

Fresh Mac

git clone https://github.com/paulsp94/omacosy.git ~/.local/share/omacosy &&
cd ~/.local/share/omacosy && ./install.sh

The clone location matters. Configs are symlinked into the repo, and macOS privacy (TCC) blocks launchd services from reading ~/Documents, ~/Desktop and ~/Downloads. If you clone there anyway, the installer falls back to copying configs; that still works, but edits then need an install.sh re-run to apply.

The installer is idempotent. It installs Homebrew if missing, runs brew bundle, compiles the helper binaries, generates the AeroSpace config from your app choices, symlinks configs (backing up anything it would replace), hides the native menu bar, applies the default theme, and starts the services.

See Permissions for the grants it asks of you, what each one is used for, and what breaks without it. Karabiner-Elements also asks you to approve its driver extension.

Updating

omacosy-update          # pull, then re-run the installer
omacosy-update --check  # just say whether there is anything new

install.sh rebuilds only the binaries whose sources changed and restarts their agents, so an update is a pull plus a re-run, and this command wraps both. It refuses a clone with local edits, and refuses one whose branch has diverged, rather than deciding either for you.

There is no background update check. The bar makes exactly one network call (the weather), and a daemon polling GitHub on a timer would quietly make that two. Nothing here contacts the network unless you run it.

Permissions

A window manager needs broad permissions, so here is the whole list: every grant, which binary asks, what it is used for, and what you lose by refusing it. Everything is refusable; the parts that depend on a grant hide themselves rather than half-work.

More on Location, because it sounds worse than it is: it buys exactly one string. The bar requests authorisation and then reads ssid(). It never asks for a position, holds no coordinate and starts no location updates. Two things are required and neither alone is enough: measured on macOS 26.3, an unbundled binary reads nil however it is authorised, which is why the bar ships inside a minimal .app. Refuse the grant and you lose the name, nothing else.

What it does not do

• No telemetry, no analytics, no crash reporting. Nothing is sent anywhere about you or this machine.
• One network call, ever: https://wttr.in/?format=j1 on a long timer, for the weather pill. wttr.in infers your city from the IP the request arrives on; no coordinates are gathered or sent, and the bar holds no location API. Delete the weather pill and nothing leaves the machine.
• omacosy's own binaries never run as root. install.sh uses no sudo, installs no LaunchDaemon, and every helper it builds runs as you, in your login session.
• Karabiner-Elements does run as root, and you should know that before installing. It is a Homebrew dependency here, purely to turn Caps Lock into Super. It ships a DriverKit system extension plus daemons that run as root (Karabiner-VirtualHIDDevice-Daemon, Karabiner-Core-Service); that is what the driver-extension approval during install is. It is the most privileged thing this repo puts on your Mac, and it is third-party. Skip it if that trade is wrong for you; you lose the Super key and keep everything else.
• Nothing here reads your keystrokes. No omacosy binary opens a keyboard event tap. Only Karabiner sees keys, which is inherent to remapping one. AerospaceSwipe's event tap is gesture-only and listen-only (1 << NSEventTypeGesture, kCGEventTapOptionListenOnly), so it cannot see or alter a keystroke. Debug logs (/tmp/omacosy-*.log) carry window titles, app names and workspace numbers, never input.

Grants are tied to a binary's code signature. With an Apple Development identity present, install.sh signs every helper with a stable identifier so rebuilds keep their grants; without one, macOS treats each rebuild as a new app and you re-grant after every install.

App choices

Keybindings launch apps defined in config/apps.conf. Defaults are Ghostty, Safari, Spotify, Slack (terminal, browser, music, messenger). Override any of them in config/apps.local.conf (gitignored), then re-run install.sh:

# config/apps.local.conf — your picks win over apps.conf
TERMINAL=Korren
BROWSER=Arc

Your personal shell config belongs in ~/.zshrc.local; the repo's zshrc wires the CLI stack and sources it.

What's inside

Why so much of it is self-built:

• AutoRaise broke on macOS 26 (cooperative activation), so omacosy-ffm focuses windows through the same SkyLight calls AeroSpace uses.
• aerospace-swipe broke because CGEvent taps stopped carrying multi-touch data. The patched version reads raw MultitouchSupport frames; the fixes are offered upstream as #29 and #30.
• JankyBorders keeps a bitmap per window and costs hundreds of MB. omacosy-borders strokes one CAShapeLayer that the WindowServer rasterizes, driven by SkyLight notifications for focus, move and resize, so the ring glides with drags without polling.
• Mission Control cannot see AeroSpace's virtual workspaces, so a workspace overview cannot be had any other way than omacosy-overview capturing them itself.
• omacosy-helper covers wallpaper setting (System Events scripting half-broke in macOS 14+), CoreAudio output switching, IOBluetooth control, cursor position, per-display notch detection, and the dwindle split hint.
• omacosy-bar holds the window model in memory and subscribes to the system's own publishers: SkyLight for window churn, IOBluetooth for connects, SCDynamicStore for the network, IOPS for battery, CoreAudio for volume, DisplayServices for brightness, Spotify's own broadcast for the track. It polls for nothing macOS announces; its only timers are the weather fetch and the clock. A workspace switch repaints in 2.5 ms because it asks no one anything; the shell bar it replaced took 164 ms to answer the same event.

The bar

One process draws all of it: bar, popups and sliders are surfaces of helper/bar.swift. Transparent bar, everything a flat radius-4 pill. A popup stays open while the pointer is anywhere in the bar or the popup, and closes when it is in neither. The bar hides itself when a window takes the whole display, and comes back if you put the pointer on the very top edge, the way the menu bar does, so brightness and volume stay reachable mid-film without leaving fullscreen. While revealed it climbs above the fullscreen window and drops back behind everything when the pointer leaves.

• Apple menu: About, System Settings, Lock, Sleep, Restart, Shut Down, Next Theme (the menu the hidden native bar took away).
• Workspaces: one segmented capsule per monitor showing only that monitor's workspaces; accent pill on the focused one; click to jump.
• Media: prev / play-pause / next + track title (Spotify). Centered on flat displays, left cluster on notched ones (per-display notch detection via NSScreen.safeAreaInsets), hidden when Spotify isn't running.
• Bluetooth: device menu (click to connect/disconnect), power toggle.
• WiFi: the pill is the icon alone; the popup names the network and adds ip and router, signal with a verdict, link rate and security generation, channel with its band and width. The name is in the popup because an SSID can be arbitrarily wide, and on a notched display a long one pushed the right cluster under the notch. The name needs the Location grant (see Permissions).
• Weather: wttr.in, cached details popup.
• Volume: scroll adjusts, click opens slider + output-device menu, right-click mutes.
• Brightness: scroll adjusts, click opens a slider (DisplayServices, no deps). Scrolling past 0 keeps going: a shade dims the display below its hardware minimum by scaling gamma, so there is no overlay window in the z-order and screenshots come out normal. It survives sleep/wake and it reaches external displays, which have no backlight API. Gamma is reset when the setting process exits, so a crash or an uninstall restores the screen by itself.
• Battery / Clock (calendar popup) / Activity (floating btop).
• Floats: appears only while the workspace holds floating windows; click surfaces the next one.

Keybindings — Super = hold Caps Lock

Karabiner remaps Caps Lock to cmd+ctrl+alt (a combo macOS never uses), so omarchy's scheme works letter-for-letter without breaking typing or app shortcuts. Caps Lock tapped alone is Escape.

Screenshots, clipboard and app switching stay macOS's own (Cmd+Shift+3/4/5, Cmd+C/V, Cmd+Tab). Alt+Tab above is the window-scoped switcher macOS lacks.

On the modifier space. omarchy layers Super+Ctrl and Super+Alt on top of Super. This setup cannot: Super IS cmd+ctrl+alt, so those modifiers are already spent and Shift is the only layer left, two against omarchy's four. Bindings that would collide are re-homed by mnemonic (lock is Super+Shift+L, not Super+Ctrl+L), and the overflow lives in binding modes instead.

Each display owns an independent set of nine workspaces, omarchy style: main holds 1–9, secondary holds 11–19. Same last digit means the same slot, and the bar and overview render only the slot digit. Super+N switches the focused monitor's slot N (via omacosy-ws); Super+Shift+N moves the window to that slot; Super+Shift+O throws the window to the same slot on the other monitor. Windows open on the workspace you're on; nothing is auto-assigned by app.

Unplugging folds the second display's workspaces into the first. AeroSpace parks 11–19 on the remaining display, but Super+N and Super+Tab only match single-digit slots, so without help every window on a secondary workspace would be stranded where no keybinding reaches it. On a monitor-count change the bar runs omacosy-ws-collapse: each occupied guest workspace empties into the lowest free 1–9 slot, occupied slots are never touched, and every moved window is recorded with its origin. Plug the display back in and they go home individually, so anything you opened while undocked stays put.

Themes

theme-set <name> switches everything at once: bar, borders, wallpaper on every display, and any terminal that follows omarchy's ~/.config/omarchy/current/theme convention (the author's does). Super+Shift+T cycles.

Themes: tokyo-night, catppuccin, gruvbox, osaka-jade. Each themes/<name>/ holds colors.toml (omarchy's 22-color palette), sketchybar.sh / borders.sh (bar and ring colors; the file keeps its omarchy name and format, and the ring uses the theme accent, omarchy's own convention), and backgrounds/ (wallpapers from omarchy's MIT-licensed theme packs). Copy a directory to add one.

Tiling: dwindle

AeroSpace natively inserts new windows as equal siblings, so three windows become three columns. Hyprland's dwindle splits the focused window along its own longer edge instead: a new window lands beside a wide window and below a tall one. That is the omarchy feel, and on a 3440-wide display it is also the difference between a usable third window and three narrow strips.

AeroSpace cannot express that rule. Its config language has no window geometry; the format variables are ids, titles and container layouts, with no width or height anywhere. So the direction is decided in code: the on-focus-changed hook runs omacosy-helper split-hint, which reads the newly focused window's frame and issues aerospace split horizontal or vertical on it.

The timing is what matters. The hint lands before the next window exists, so AeroSpace places that window correctly in its first pass. An earlier version was a daemon that re-nested windows after AeroSpace had already placed them, and you could see it: the screen laid out twice, about 250ms apart. What remains now is the new window's own first frame, which appears about 150ms before AeroSpace tiles it. No window manager can place a window that does not exist yet.

Two implementation notes. enable-normalization-flatten-containers is off, because it dissolves the very container split creates (AeroSpace prints a warning saying so if you try). And the hint waits for the window's frame to hold still before reading it, then names its window with --window-id instead of trusting "the focused window". Both guard against the same thing: a new window fires the hook too (it takes focus on open), at a moment when its frame is still the app's default shape and another window may grab focus before the hint lands. One hook covers both hover and keyboard focus: AeroSpace notices the focus omacosy-ffm moves, even though ffm moves it through SkyLight.

Manual control (Super+J flips, resize, float) works unchanged.

Floats get a rescue path, because macOS will not keep them on top: z-order is per app, not per window, so a float sinks behind whichever app you focus next, and pinning it would need a private call with SIP off. Instead the bar grows a pill whenever the focused workspace holds floats, and Super+S or a click on that pill surfaces the next one and brings the cursor with it.

Focus follows mouse & swipes

omacosy-ffm: hover focuses, with no raise over floating windows, so floats stay in front. It is event-driven off mouse movement, so a parked cursor never steals focus from a launching window. It never changes focus during drags, and never through an always-on-top panel: hovering a Touch ID prompt leaves focus exactly where it is instead of falling through to the window beneath. Per-app opt-out lives in config/ffm-ignore (omarchy's JetBrains-style exception).

4-finger swipes left/right switch workspaces on the display under the cursor (native-Spaces semantics), with wrap-around, on any trackpad. The system's own 4-finger gestures are disabled by macos-defaults.sh so Mission Control never fights the daemon; uninstall.sh restores them.

Workspace overview

4-finger swipe up: the wallpaper breathes in behind a dim wash and every non-empty workspace of the cursor's monitor gets a card (per-display Mission Control semantics), with live window previews (ScreenCaptureKit, composed into the tile layout), app icons, and an accent ring on the focused workspace. Click a card or press its digit to jump; empty workspaces show as small chips, and digits work for them too. Swipe down, Esc, or a backdrop click dismisses. It is a resident daemon, so it opens instantly.

Drag a card to reorganize: the row makes room as you move, and the drop slides everything between the old and new position over by one. AeroSpace workspaces cannot be renamed or resequenced (the name is the position), so what actually moves is their windows, which means a split layout inside a moved workspace comes back as a flat row. Dropping a card on an empty chip moves that workspace there instead.

Parking the setup

omacosy-toggle off returns to a vanilla Mac in one command (AeroSpace stops managing, all daemons and the bar stop) without uninstalling; omacosy-toggle on brings everything back. No argument flips.

Memory use

About 157MB of physical footprint (what Activity Monitor calls Memory) across WM, bar, three background daemons, the swipe daemon and Karabiner, measured docked to a second display. Resident set size reads ~322MB, but RSS counts each process's share of the same shared system frameworks more than once, so footprint is the number to compare. Largest first:

On one display the same set measured ~155MB; the bar and the border overlay each draw per-screen, and AeroSpace carries a second workspace set. The figures move with uptime. omacosy-overview caches a half-resolution capture per window shown, so it starts near 9MB and settles around 37MB; it plateaus there rather than climbing, because the cache is refiltered to the visible set on each open. AeroSpace drifts the other way, reading higher the longer it runs. Packaging the bar as an .app (which is what unlocks the wi-fi network name) cost about 1MB; the bundle is a directory and an Info.plist, not a second copy of anything.

Back to a normal Mac

Manifest-driven: install.sh records what this machine actually gained (Homebrew packages that weren't already present, cloned repos, every defaults key's prior value), and uninstall.sh removes and restores exactly that. Tools and settings you had before omacosy are never touched. Pre-manifest installs fall back to a conservative teardown that leaves all Homebrew packages in place.

License & credits

MIT (see LICENSE). Standing on: omarchy (the whole idea, plus MIT-licensed theme palettes and wallpapers), AeroSpace, Karabiner-Elements, aerospace-swipe (MIT; patched here for macOS 26, fixes offered upstream).