Start Here

Installing

Oniomarchy installs onto a working Omarchy system. You don’t reinstall anything and you don’t boot an ISO — you run one script and the security layer lands on top of the desktop you already have.

What you need first

• Omarchy, already installed. Oniomarchy builds on top of it, so it’s the one thing that has to be there first.
• Your user password. You’ll be asked for it once, at the start.
• Room and a little patience. It’s a big toolkit — expect a sizeable download and a real install, not a thirty-second one.

If Omarchy isn’t there, the installer says so and stops rather than making a mess — so there’s nothing to get wrong.

Getting it and running it

git clone https://github.com/SalimRK/oniomarchy.git
cd oniomarchy
./install.sh

That’s the whole thing. The script primes sudo once, then works through the install in order: preflight checks, the applications, the Security menu, the services, the privacy plugins, the Trigger menu, and the theming.

Options

./install.sh            # the normal run — quiet, with a live progress line
./install.sh --verbose  # show every pacman / yay line as it happens
./install.sh --help     # full usage, including the two below
./install.sh --log PATH # write the run log somewhere specific
./install.sh --no-log   # don't write a log file

The normal run is quiet on purpose. Instead of a wall of package-manager output, you get one live line that redraws in place — the oni banner at the top, then the current step, a progress bar, and a counter. A step that runs long enough to look stuck starts showing its own latest log line underneath, so you can tell “installing a huge dependency tree” apart from “hung.” A step that fails drops out of the quiet view and prints its last thirty lines right there, so you see the actual error without going digging. Reach for --verbose when you want the firehose.

It always writes a log

Every run, in either mode, writes a full log to:

~/.local/state/oniomarchy/install-<timestamp>.log

along with a latest.log symlink pointing at the most recent one. That’s outside the repo on purpose, and it’s the first thing to look at if something didn’t go the way you expected. Use --log PATH to put it elsewhere, or --no-log to skip it.

If a tool fails

The toolkit is big, and the internet is the internet — occasionally a single package fails to download or an AUR build breaks upstream. Oniomarchy is built so that one failed tool doesn’t sink the whole install. If a tool won’t install, the run notes it and keeps going — you still get the Security menu, the services, the privacy layers, and every other tool. At the end it tells you plainly what didn’t make it, so a partial install never passes itself off as a clean one and you know exactly what to look into.

When it’s done

You’ll have the full Security menu in your launcher, the Trigger → Pentest menu with the listener and services, the Tor and MAC bar panels, the hardened Firefox ready to go, and Oniomarchy’s branding on your themes. The next page walks you through finding all of it.