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

The whole desktop environment idles at about 157MB of physical footprint — what Activity Monitor calls Memory — across WM, bar, three background daemons, the swipe daemon and Karabiner. Resident set size reads ~322MB, but RSS counts each process's share of the same shared system frameworks, so footprint is the honest figure. Measured on this machine docked to a second display, largest first:

A second display is not free: the bar and the border overlay each draw per-screen, and AeroSpace carries a second workspace set. On one display the same set measured ~155MB. The dwindle daemon used to be on this list; the split direction is decided by a short omacosy-helper run on focus change now, so nothing resident does it.

These figures move with uptime, so treat them as a band rather than a constant. omacosy-overview is the swing: it caches a half-resolution capture per window shown, so it starts near 9MB and settles around 37MB — measured over repeated opens, it plateaus there rather than climbing, because the cache is refiltered to the visible set each time. AeroSpace drifts the other way, reading higher the longer it runs. Packaging the bar as an .app (which is what buys the wi-fi network name) cost about 1MB — the bundle is a directory and an Info.plist, not a second copy of anything.

It is mostly self-built: five small signed Swift binaries replace what would otherwise be a pile of dependencies (several of which are broken on macOS 26 — see below).

Posture: built for macOS 26 (Tahoe) on one desk — a MacBook Pro plus one external display. It generalizes deliberately (roles instead of hardware names, per-display notch detection), but "works for me" is the honest tier. The permission setup is real work. Issues and PRs welcome; support promises are not made.

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 — a clone there makes the installer fall back to copying configs (still works; edits then need an install.sh re-run to apply).

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 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 while broadcasting when the machine is awake. Nothing here contacts the network unless you run it.

Idempotent — re-run after pulling changes. 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 services.

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

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

On Location, the one that sounds worst: it buys exactly one string. macOS classes the wi-fi network's name as location data, so nothing here can name your network without it. 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 it and you lose the name, nothing else.

• 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, and you should know that before installing. It is a Homebrew dependency here, purely to turn Caps Lock into Super — and 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 single 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.

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.

Why self-built: on macOS 26, cooperative activation broke AutoRaise (focus-follows-mouse), CGEvent taps stopped carrying multi-touch data (breaking aerospace-swipe upstream — fix PRed as #29/#30), and JankyBorders' per-window bitmaps cost hundreds of MB. omacosy-ffm focuses via the same SkyLight calls AeroSpace uses; omacosy-borders strokes one CAShapeLayer the WindowServer rasterizes, driven by the window server's own event stream (SkyLight notifications for focus, move and resize — no polling, the ring glides with drags); omacosy-helper covers wallpaper (System Events scripting half-broke in macOS 14+), CoreAudio output switching, IOBluetooth control, cursor position, and per-display notch detection. omacosy-overview exists because Mission Control cannot see virtual workspaces, so a workspace overview cannot be had any other way. omacosy-bar is the status bar itself: one process holding the window model in memory and reading its 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 — so 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.

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 down 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 (real 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 is as wide as it likes, and the right cluster is right-aligned — on a notched display a long one pushed the far end of the cluster under the notch.) The name needs the Location grant, because macOS classes an SSID as location data (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 fails safe: gamma is restored if the bar ever exits. It reaches external displays too, 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.

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 = 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 ever 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.

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; 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.

AeroSpace natively inserts new windows as equal siblings (three windows = three columns). Hyprland's dwindle instead splits the focused window along its own longer edge, so a new window lands beside a wide one 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 it: 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. on-focus-changed runs omacosy-helper split-hint, which looks up the newly focused window's frame and issues aerospace split horizontal or vertical on it.

The point is the timing: the hint lands before the next window exists, so AeroSpace places that window correctly in its first pass. This used to be a daemon that re-nested windows after the fact, and you could see it — the tiler laid out twice, ~250ms apart. Deciding beforehand leaves one layout and nothing to correct. What is left is the new window's own first frame, which appears ~150ms before AeroSpace tiles it; no window manager can place a window that does not exist yet.

Two details make it work. enable-normalization-flatten-containers is off, because it dissolves the very container split creates — AeroSpace tells you so if you try. And the hint names its window with --window-id rather than trusting "the focused window", because a window that opens inside that ~90ms gap takes focus with it. 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 mean rewriting the window's level through a private call with SIP off. Instead the bar grows a pill whenever the focused workspace is holding floats, and Super+S — or a click on that pill — surfaces the next one and brings the cursor with it, so a float is never lost behind a tile and never retrieved by aiming at something you cannot see.

omacosy-ffm: hover focuses (no raise over floating windows — floats stay in front), event-driven off mouse movement so a parked cursor never steals focus from a launching window, never during drags, 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 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), wrap-around, 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).

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) — live window previews (ScreenCaptureKit, composed into the tile layout), app icons, the focused workspace accent-ringed. Click a card or press its digit to jump; empty workspaces show as small chips (digits work for them too — straight to a clean screen). Swipe down, Esc, or a backdrop click dismisses. 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.

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.

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.

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).