omabox up
Start a box: headless and invisible unless you ask for a window, any screen size or several monitors, on the theme you name, with your plugins, an isolated network or a save to start from.
$ omabox up $ omabox up --size 2560x1440@144 --plugin ~/code/myplugin $ omabox up --monitor 1080x1920 --monitor 2560x1440,scale=1.6,below $ omabox up --theme-dir ~/code/my-theme --theme my-theme $ omabox up --net isolated --allow 8081
omabox up [NAME] [--size WxH[@HZ][,scale=S]|host] [--interactive] [--plugin PATH|ID]... [--overlay DIR]...
[--ro-bind DIR[:DEST]]... [--seed SRC:DEST]... [--net isolated [--allow PORT,...] [--addr ADDR]...|host]
[--env KEY=VAL]...
[--no-seed extensions,fonts] your plugins' settings files, your fonts left on the desk
[--theme-dir DIR]... a theme you are editing, live, in the box's themes/
[--theme NAME] start on that theme, not your desktop's current one
[--monitor WxH[@HZ][,scale=S][,right|below|X,Y]]... more monitors
[--idle DURATION] [--stock-bar] [--systemd] [--xwayland] [--autoreload] [--no-shell] [--from SAVE]
[--desk-shell] your desktop's whole shell: every plugin, shell.json, their files
[--audio] [--polkit] its own PipeWire (a silent mic); a polkit agent can register (polkit ask)
[--no-pointer] [--dnd] [--no-dock] no pointer (pointer show); Do Not Disturb on; 4.5's dock off
[--stock | --clean [--keep animations,bar,clock,fonts,identity,locale,pointer,wallpaper]] a new user's look; --clean: frozen too
[--hyprland PATH] a Hyprland build or folder of yours, not the installed one
[--quickshell PATH] a Quickshell build of yours for the box's shell
[--omarchy DIR | --desktop plain|desk [--shell CMD]] an Omarchy tree (a checkout); plain: nothing of Omarchy's, CMD its shell; desk: plain at your HOME's path
[--workspace WS] [--confirm-close | --no-confirm-close] (interactive)
[--new] start it under a free name, box-1, box-2, ... (printed)
[--json] the box as ls --json lists it, on stdout
omabox help up
NAME defaults to $OMABOX, else the current git repo's name, else "default". In an agent session (Claude Code, Codex, guard exec) that name gets the session's id, myrepo-5cc72cdc: one box per session, gone when its agent exits. OMABOX_SESSION= (empty) turns that off. A git worktree is named by its own folder, so each worktree has its own box. Outside any repo (a scratch dir) the name is default-SESSION; with no box of that name, every command but up uses the session's one box started from its repo, said once: down too, so omabox down there takes that box down. A down whose name has no box, while the session has boxes up started elsewhere, names each with the down -b that takes it, and exits 1.
-b NAME (or --box NAME) picks the box, in every command that takes one; it goes before the command too (omabox -b NAME windows).
Every box has its own network (pasta): by default the internet, the LAN and your servers. Across the box boundary use 127.0.0.1, not localhost; a box's servers appear on your 127.0.0.1 about a second after they listen, one box per port (a box server on a port the host or another box has fails to start, address in use; of two started within a second, only one gets it there: omabox ports names the holders). --net isolated: a loopback and the --allow ports only, which are for reaching those host ports from the box: pasta listens on each in the box, so a box server on one fails, address in use (ports: allowed); serve on another; --addr ADDR (repeatable) puts an address on that loopback, for an app that wants a peer from a non-local address: one in a documentation range (192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24, 2001:db8::/32). A server on 203.0.113.10 sees a client bound to 203.0.113.11 come from there. --net host (asked for by name only; no config picks it): your host's network itself, no pasta, for a tool that scans the real LAN. The box keeps its own seat, session bus, runtime dir and HOME, but its servers take your host's real ports (they collide with your services and other host boxes; nothing is forwarded, ports: host-net), it sees your real interfaces and its ARP and ICMP reach your LAN. Not for code you do not trust. Refused with --allow, --addr, --xwayland (its X server would be your host's), --desktop desk, inside ai-jail, and while protect-ports names a port.
run starts the command with the box's environment, not yours: --pass VAR hands it one of your variables (a password too: never on a command line); --env-file FILE hands it a file's KEY=VAL lines (a dev.env: read as data, nothing expanded; --pass wins); keys --pass VAR types one (never -t for a secret: the process list shows it). keys -t and keys --pass type newline and tab (Return, Tab); any other control character is refused (exit 2); a value's one trailing \r is dropped. --env KEY=VAL is the box session's, on up (and a throwaway run's box); run --env on a box that is up hands it to the command, as --env-file does (--pass wins). Never what the session sets itself (PATH, HOME, XDG_RUNTIME_DIR, XDG_*_HOME, WAYLAND_DISPLAY, DISPLAY, HYPRLAND_INSTANCE_SIGNATURE, LD_PRELOAD, OMABOX_BOX...), by any of them.
--seed SRC:DEST: a file or folder of yours copied into the box HOME at DEST (.config/x or ~/.config/x) before its session starts, for a plugin that reads its config once at start; the same refusals as --ro-bind (no secret stores; nothing in ~/.config/omarchy but plugins/ and themes/). A copy: the box's changes stay in the box; a link already in DEST is replaced, never written through. Never into a --plugin's or --theme-dir's folder there (refused: it would replace the plugin or theme): write the file in that folder instead.
--no-seed extensions: the box starts without your ~/.config/omarchy/extensions (the plugins' settings files, the menu's extension), with a new Omarchy user's (/etc/skel's; a --from save's own stay). Otherwise up copies it, and says each file a --plugin's code names there ("seeded extensions/NAME.json from your desk"): that plugin starts on your desk's settings, an on/off switch in them too. --no-seed fonts: the box starts without your fonts. Otherwise ~/.local/share/fonts and ~/.fonts are mounted read-only at the same place in the box HOME (ls --json: desk_fonts), so a theme's or a plugin's own faces draw as on your desk (not in a --stock box, nor a --clean one unless --keep fonts; nor when the box HOME has its own folder there, a --from save's or a --seed's: it keeps that one). A link in them that leads out of them is not in the box (said). Comma-separated, repeatable.
--theme-dir DIR: a theme you are editing, live: the box HOME's ~/.config/omarchy/themes/NAME (DIR's name) is a link to DIR at its own path, in place of the copy up makes of each of your themes. The box has DIR there when it is in the repo you run from, a same-path --ro-bind or an --overlay; any other DIR is mounted read-only there, refused as --ro-bind's are. omarchy-theme-set NAME in the box applies it, as it is then.
--theme NAME: the box starts on that theme (Omarchy's, one of yours or a --theme-dir one; checked before anything is made), not your desktop's current one: omarchy-theme-set NAME runs in the box before its Hyprland and bar start, so a test gets the same look whatever your desktop is on (its background: your own first for NAME, else the theme's; with --stock the theme's). Over a --from save's look too. up again with another is refused.
--stock-bar: Omarchy's default bar (its shell.json, no shell.toml), not a copy of yours: for shots, sizes and colours as most people see them. --theme leaves your bar as it is; without this up says when that bar is not Omarchy's ("seeded the bar from your desk: its shell.json layout and shell.toml [bar]"). Plugins are placed as without it. --stock: the rest of a new user's desktop too.
--no-shell: Hyprland only, no Omarchy shell (faster; no bar, tray or notifications). --desktop plain (#247): the box's Hyprland runs omabox's own small config (Hyprland's defaults, your keyboard layout from /etc/vconsole.conf, SUPER+RETURN a terminal, SUPER+W closes) and sees an empty /usr/share/omarchy, as on a machine without Omarchy: no shell but --shell's, and a HOME with none of your Omarchy look (git's name and email only). --plugin, --theme, --theme-dir, --stock-bar, --stock, --desk-shell, --omarchy, --dnd and --no-dock need Omarchy and are refused, as are the dnd, dock and plugin commands on the box. Without --desktop: omabox config desktop's, else omarchy where Omarchy is installed and plain where it is not (up says so; doctor and setup test the same); --omarchy DIR is an Omarchy box. ls says a plain box's desktop (and shell) under its line. --desktop desk (#321): your own desktop in a box, its HOME at your HOME's path ($HOME in the box is yours), so what names your paths finds the box's: still the fake HOME, never your files (but the repo, --ro-bind, --seed's and the copy of your desktop). From the host it is <dir>/home, as any box's; a path under your HOME in a command is the box HOME's there, not yours (run says so). A mount (--ro-bind, --overlay) goes inside that HOME, never at it or above it, over omabox's own files in it, nor through a link in it. up copies in your ~/.config/hypr (links followed, as copies), the config and state of the shell it finds, and the images they name, before --seed's; never a secret store or what looks like a key, capped, what it left out said (box.json desk_copy). It needs a Lua config (a hyprland.conf alone is refused: hyprctl eval refuses it). Its base is your desk's: Omarchy's (Omarchy here and your hypr/hyprland.lua loading it: an Omarchy box, its shell Omarchy's with your plugins and shell.json, as --desk-shell copies them; it takes --plugin, --theme, --theme-dir, --dnd, --no-dock and --omarchy, refuses --stock, --stock-bar and --keep), else plain. Its Hyprland runs your copied hyprland.lua; what it starts goes through an autostart policy (idle and lock daemons, your systemd session, system-bus applets, what the box runs itself are dropped; binds run as on your desk), each decision a line of omabox log autostart. Its idle is held off (tools/idlehold): your shell's idle timeouts never lock or blank it. On a plain base its shell is the one your config starts (DMS, Noctalia, Caelestia, Waybar, a Quickshell config), run in the box's shell slot as --shell's: up waits for it and says which, and ls, pid shell, log shell and restart-shell work on it; a second shell your config starts is dropped. --shell CMD runs another in its place, --no-shell none; a config that starts none omabox knows fails up, saying so. Refused with --desk-shell (part of it; alone it still works, with a note), --clean (the path carries your login name) and inside ai-jail (not yet); omabox config desktop does not take desk yet, and check run --desktop desk is refused (a check needs the same box every run). --shell CMD (#247, plain only): the box's shell is CMD (dms run, qs -p DIR, caelestia shell -d), run by sh in the session; the shell is all CMD starts (#438): a launcher may start it and exit, and the shell is gone once nothing of it is left. up waits until one of its processes draws a layer (OMABOX_READY_TIMEOUT), says when it exits or crashes on the way; log shell is its output, restart-shell stops all of it and starts CMD again, a Quickshell crash of its config is the shell's. An app the shell starts itself counts as the shell (not one through hyprctl dispatch exec). --quickshell PATH: the build is CMD's qs and quickshell (on the session's PATH).
--stock: Omarchy as a new user sees it, for a showcase or a shot for someone else: Omarchy's bar (--stock-bar) on tokyo-night (or --theme) with the theme's own wallpaper (never yours for it), English (en_US.UTF-8, else C.UTF-8) in UTC for the whole session, and nothing of your desk's look: not your terminal configs and terminal choice, branding, themes (but the one --theme names, when it is yours and not Omarchy's), wallpapers, plugins' settings (as --no-seed extensions), Hyprland toggles or fonts; a new user's HOME (/etc/skel's) instead. The clock, pointer, network and animations are as in any box; --plugin, --theme-dir and the rest work on top (ls --json: stock, a clean box's too). Your git name and email stay (git config --global user.name and user.email, so a commit in the box works): a shot of a git log shows them. Over a --from save, the save's HOME stays as saved (said); the bar, theme and locale are stock. Not with --desk-shell.
--clean: --stock plus the run-to-run freezes, a desktop where only what is tested moves, for shots compared across runs (check): a #ff00ff wallpaper (no theme has it: any of it inside a window or the bar is a hole), the bar's clock frozen at "Friday 12:00" (in its place, at its width), no pointer, no network (--net connected gives it back), animations off (over reloads too), and no name of yours: the user is user (no full name) and the host omabox. --keep LIST takes any of animations, bar (yours), clock, fonts (yours), identity (your user and host names), locale (yours and your timezone), pointer, wallpaper (the theme's) back. A theme set later in the box brings that theme's wallpaper. On a plain box: no bar, theme or clock (--keep bar and clock refused), and the sentinel is its Hyprland's background colour (misc:background_color), not a wallpaper.
--audio: the box's own PipeWire, WirePlumber and pipewire-pulse (PipeWire and Pulse apps both play), its only devices a speaker nobody hears (omabox-speaker, a null sink: the default output) and a silent microphone (omabox-mic, the default input). Nothing reaches your audio: a box has no /dev/snd and its own runtime dir (its sockets, never yours). audio says whether the box made a sound, record --audio puts it in the video (AAC). Logs: log audio. Without it a box has no audio.
--polkit: a polkit agent in the box (the shell's polkit plugin, a copy of it under test, a GTK or Qt agent) registers and is asked, as on a desktop, and the end of each request is the agent's own. A box has no system bus and no logind session, and never gets yours: it gets a system bus of its own where only polkit's name can be owned, by a stand-in authority, which keeps the agents as polkitd does (one per session, dropped when they leave the bus) and makes a request only when polkit ask does. In place of PAM it answers polkit's agent helper with a password prompt, and takes the one password ask --accept names (a test's, never yours). It decides nothing for any service: pkexec, pkcheck and mechanisms get no answer from it. The bus is the box's (its processes share one uid, so one can answer in the stand-in's place): what polkit prints of it is bounded and plain. The box's processes are in a session named "omabox" (XDG_SESSION_ID). Logs: log polkit.
--autoreload: the box's Hyprland reloads its config when a file it loaded changes, as a desktop's does; a box turns that off, so an update of omabox or Omarchy leaves it as it is. For a project that must see what a file change does (a helper rewriting a file the config loads, on a Hyprland event, reloads for ever). Its config is still the box's own copy; an Omarchy update reloads it too.
--plugin PATH|ID: a shell plugin, read-only, enabled where its manifest says; up and restart-shell warn when Omarchy's validator or the shell refuses it (ls --json: plugin_status). One the box has at its own path (in the repo up runs from, a same-path --ro-bind or an --overlay) is linked to there, as on a desk, so readlink -f leads into its repo; any other is mounted (plugin_status: via).
plugin add PATH|ID puts a plugin in a box that is up as --plugin would have: read-only, linked to where the box has it at its own path or mounted, made known to the shell (a rescan, until it lists it) and enabled, its state said (ls --json: plugin_status). plugin remove ID takes one out (one from up's --plugin too): disabled, unmounted or unlinked, rescanned. A link made by hand in the box HOME works only for a folder the box has at its own path, and omarchy plugin enable right after rescanPlugins says "is not known" until the rescan is done; plugin add does both. Not inside ai-jail, nor on a box a jail started (up --plugin there).
--desk-shell: your desktop's shell as it is, to check a plugin against a real desk: every plugin in ~/.config/omarchy/plugins (read-only, as --plugin's; a --plugin of the same id wins: your working copy) but omabox's own widget (it lists your boxes; --plugin mounts it), your shell.json unfiltered (only idle held off: a box has no real input; omabox's widget taken out of it), and the other files in ~/.config/omarchy your plugins read (a plugin's JSON, a folder beside shell.json) copied into the box's. Never api-keys.env nor anything named or holding a key, token, secret, password, credential, auth, cookie or session (any .env, .pem, .gpg...), hooks/ (your scripts), a git dir or a backup; regular files up to 1 MiB (16 MiB, 1000 in all); a link only to a file inside the folder. up says what went in and what did not, and why (ls --json: desk_shell). Not with --stock-bar or --stock; not inside ai-jail.
--hyprland PATH: the box runs that binary (its folder mounted read-only at its own path) with the box's aquamarine, so a build must link a libaquamarine soname the box has (checked before the box starts); hyprctl and hyprpm stay the installed ones (a warning when the versions differ). PATH may be a folder, mounted whole: an unpacked package (usr/bin/Hyprland, as bsdtar -xf leaves one, its libraries in usr/lib), an install prefix (bin/Hyprland, lib) or a build folder (Hyprland, hyprctl/hyprctl); its libraries come first (its aquamarine is the box's) and its hyprctl is the box's. OMABOX_HYPRLAND=PATH is the default for every up (a suite on another Hyprland). ls and windows name it. Compositor logic runs for real (layouts, focus, input routing, the Lua config, IPC, protocols); DRM/KMS, real monitors, HDR/VRR, multi-GPU, libinput with real devices and the session and suspend paths never run in a box (the lock screen does, without a real password). --quickshell PATH: the box's shell (and quickshell/qs on its PATH, and omabox's own calls to its shell) runs that binary, its folder mounted read-only at its own path. Quickshell uses Qt's private API, so the build must be one against the installed Qt: up refuses a build against another Qt, or one needing a library the box lacks, naming both. ls and windows name it; ls --json has quickshell_version (quickshell --version in the box, every box's), which is the last release's number, never proof that a fix is in: a build of an unreleased commit says it too.
shot --no-pointer (a screen shot, --burst too) and record --no-pointer leave the pointer out, for stills and videos meant for people (no arrow on the app, none parked on a hover state): it is hidden (Hyprland's cursor:invisible), a frame without it awaited (up to a second), and shown again after, as it was, also on a failure or Ctrl-C; a recording keeps it hidden until record stop. pointer hide (or up --no-pointer) hides it in the box until pointer show, over config reloads and theme switches (omarchy-theme-set reloads). Hidden, it still moves and clicks where it is told, focus still follows it, and peek's marks still show it; wait and --changed leave out where it is, as they do when it shows.
$OMABOX_READY_TIMEOUT: how long up waits for Hyprland and the shell (default 30s).
Interactive boxes and peek windows open on workspace 9, without focus: omabox config workspace WS (1-99; special:omabox, a special workspace of omabox's own: the bar widget's Show opens it, a workspace switch hides it; special:NAME; special = Omarchy's scratchpad on SUPER+S, on 4.5 its Quake console) or --workspace. A peek window shows click, pointer and keys for ~3 s (a ring, key captions, --pass values as *); never the box's own frames.
Closing an interactive box's window ends the box; omabox config confirm-close on asks first (a second close is a yes). A headless box renders on the first GPU; omabox config gpu lists them, and omabox config gpu nvidia (amd, intel, a driver's name, or a PCI slot: two GPUs of one kind) picks another; up falls back to the first, saying so and why, when that one is not there (a card handed to a VM). The first is one that renders: a VM's virtio-gpu without virgl (software only) comes after any other, and when it is the only one up refuses it before starting a box that would die there. $OMABOX_RENDER_NODE overrides it. An interactive box renders on the GPU your desktop's compositor uses, whatever the setting. omabox config protect-ports 8080,5432 keeps those host ports from every connected box, through any of the host's addresses (an isolated box's --allow refuses them; default removes them; it needs nft). omabox config desktop plain (or omarchy) is the desktop of a box up gets without --desktop; auto, the default, is Omarchy's where Omarchy is installed and plain where it is not.
aquamarine's fix for nested Wayland outputs (hyprwm/aquamarine#415, until the system's has it: a release, or a package patched with it; omabox looks for what the fix added, not the version): a headless box on an NVIDIA render node and confirm-close need it, and up refuses them without it; omabox setup --aquamarine builds it (a checkout's build/prefix, else ~/.local/share/omabox), with omabox's own fixes for interactive boxes on top: a key held when the window loses focus is released, and in a monitor's window your pointer lands on that monitor and your cursor stays shown. No system aquamarine has those, so it builds even when the system's has the fix; it builds nothing only when boxes already use this omabox's build (--force rebuilds it). It builds the aquamarine the installed Hyprland links: 0.15.1 with the fix for Hyprland 0.56 (libaquamarine.so.14), 0.16.0 for Hyprland 0.57 (.so.15; there Hyprland itself puts the pointer on the right monitor). For a Hyprland that links another, it builds nothing, says so and exits 0: boxes use the system's. omabox --version says which one new boxes use: a private build, or the system's (with the fix, patched with it, or without it). A git worktree of omabox with no build of its own uses its main checkout's build/prefix, and says so. OMABOX_AQUAMARINE=system: the system's aquamarine all the same (testing).
SUPER + ALT + ESCAPE toggles sending SUPER keys to an interactive box, once: until focus leaves it, or a key is pressed with the pointer off it. keys-to-box on makes them follow focus and the pointer, for the box's lifetime: its window has focus and the pointer is over it, SUPER is the box's; focus goes elsewhere or the pointer leaves it (your bar, another monitor), it is yours, and the pointer back over it gives it to the box again. SUPER + ALT + ESCAPE over the box gives the keys back until the box loses focus and gets it again. No argument prints on or off. While keys go to a box, its window's border takes the theme's red and the bar widget's icon is lit.
--dnd, dnd on: the box's Do Not Disturb, in its own Omarchy shell (never your desktop's): new notifications stay off its screen, so no toast lands over a window's corner between steps (Omarchy still shows a critical notify-send, a verification code and its own action toasts, such as a layout change's). --dnd also dismisses any toast up when the box is ready; dnd --clear does that at any time. Bare dnd prints on or off. A box --from a save keeps the save's (Omarchy 4.5 keeps it in its notifications state). --no-dock, dock off: Omarchy 4.5's dock disabled in the box's shell (its shell.json's disabledPlugins, as omarchy plugin disable omarchy.dock writes it), its layer gone. The dock shows only on a floating workspace; elsewhere its layer stays mapped, taking no input. Bare dock says, per monitor, whether it is shown (its icons take input), tucked away (auto-hide or a maximised window: only the strip along its edge, until the pointer reaches it) or hidden (none); --json the same as an object. Both refuse a box with no shell; dock one whose Omarchy has none (before 4.5).
A headless box goes down after $OMABOX_IDLE (default 2h) with no omabox command against it, no peek window and no omabox run still running; --idle 30m|2h|0 (never) per box. Interactive: never. Write the unit: a bare --idle 45 is refused (minutes up to 0.9, seconds everywhere else).
A run -d job is not activity: a server only polled over HTTP needs --idle 0 (or longer). At --idle 0 a session's box still goes with its agent (ls says never); a box with another name (-b NAME) stays.
A headless box at --idle 0 with no agent to go with stays up until down. Once what started it is gone (the script or agent whose command ran up), ls says orphan under IDLE (ls --json: orphan) and down --orphans takes those down; nothing does by itself. One you started at a terminal, outside an agent session, is yours: never an orphan. A session's subagents share its id, so its default name. ls says under each box where it was started and by which agent session (and who used it last, when another; ls --json: dir, session). A down of a box another caller started or used in the last 10 minutes warns that it may be another agent's, and still takes it down; the name's next command says when a down took it, and from where.
Sizes: WxH is @60; host copies your focused monitor's size and refresh rate (scale stays 1). ,scale=S (1 to 4, as a monitor's) gives the main screen a scale, headless only: --size 3840x2160,scale=2 is a 4K screen laid out as 1920x1080, the bar and apps their usual size in twice the pixels, so a shot of it is 3840x2160 (coordinates stay the layout's: click --in maps a shot's). mode WxH without one is scale 1. Hyprland may round a scale to whole pixels (mode says so). Measure rendering cost with omabox gpu (and omabox cpu) in a box whose mode matches your monitor.
More monitors: up --monitor SPEC (repeatable) or monitor add SPEC on a running box. SPEC is WxH[@HZ][,scale=S][,right|below|X,Y]: placed right of the last one made by default, or below it, or at X,Y in the layout (which starts at 0,0 on the main screen: no left or above). Scale 1 to 4; Hyprland may round it to a whole-pixel size (2560x1440 at 1.5 becomes 1.6). The main screen (--size, mode) is HEADLESS-2; the others HEADLESS-3, -4, ... (or --name); on NVIDIA, where a box draws on Wayland outputs, WAYLAND-1 and WAYLAND-2, -3, ... (no --name); there a headless output a program makes itself (hyprctl output create headless) is listed 0x0, which monitor list and shot say, naming a box on another GPU to test it in. monitor remove NAME unplugs one: Hyprland moves its workspaces to the others. They survive a config reload, and one placed right or below moves when the one before it changes size (mode, said) or goes; an X,Y one stays. Coordinates (click, drag, pointer, pixel, -g) are the layout's (pixel refuses a point in a gap between them); shot --monitor NAME takes one monitor (a shot of a mixed-scale layout comes out at the highest scale: --fit). peek shows the main screen, peek --monitor NAME another: a window per monitor, tiled on the workspace, each marking the clicks and pointer on its own monitor (keys on all); one whose monitor drops (output drop) says it is gone, and shows it again once it is back; the whole layout at once is shot. An interactive box's monitors are windows on your desktop, on its workspace, placed in the box as a headless box's; on your screen the box's layout scaled as a whole, as display settings draw it: one scale for every window (at most 1), the picture centred on the monitor its main window is on, the main window floated for it (it tiles again when the last monitor goes); each monitor add and remove lays it out again. Each window is a view of its monitor: the monitor's size in the layout, which the bar and apps see, is the one asked for (the main screen's --size, a SPEC's), its mode its window's pixels at a scale of at most 1 (monitor list). Resizing a window changes its view's scale, not the monitor (a window of another shape shows it smaller along one side); closing one unplugs it. They need aquamarine's fix, as NVIDIA boxes do, and omabox's build of it puts your pointer on the monitor whose window it is in and keeps your cursor shown from one window to the next (monitor add says when a box's aquamarine does neither).
Crashes in a box skip the desktop's crash notifications (core limit 1 byte; raise it inside for a core).
A save keeps what a box's apps set up (signed in, a PIN, a library): the box HOME without .cache and its logs, keyring included, paused for the copy. up --from starts with it, then seeds your Omarchy look on top as for any box (theme, bar, terminals: today's, or --theme's, not the save's). Close an app first for a clean save. Saves live in ~/.local/share/omabox/saves until saves rm.