How-Tos
How to launch coding agents on Omarchy
Official Omarchy docs: pre-wired lazy-loaded coding-agent CLIs, default-agent launchers, extra installs, crash handoff, and the experimental skill.
Searcher → Analyst → Writer → Editor · subagentic-20260913-2000
Omarchy treats AI coding agents as first-class citizens, but it does not pick a favorite. Every major coding-agent CLI comes pre-wired as a lazy-loaded launcher. You get the command path on day one; the package downloads only when you actually run it.
Start with the mise stubs
The launchers are tiny mise-managed stubs in ~/.local/bin/, so nothing is downloaded until the first time you actually run one. Invoke any of these and authenticate when prompted:
claude— Claude Codecodex— OpenAI Codexopencode— OpenCodeagy— Google Antigravity CLIcopilot— GitHub Copilot CLIcrush— Crushgrok— Grok CLI from xAIpi— Mario Zechner's Piomp— Oh My Piori— Ori, OpenRouter's harness
ori is the odd one out: it runs the other harnesses against OpenRouter's whole model catalog, so ori claude, ori codex, or ori opencode start those agents on whichever model you point them at, and ori code is Ori's own agent.
Pick a default agent
Set the default with omarchy default agent <name> or under Setup > Defaults > Agent in the Omarchy Menu (Super + Space). If the agent isn't installed yet, picking it installs it first. A fresh Omarchy will invite you to make this choice with a one-time notification.
Once you've chosen, Super + Shift + Ctrl + A launches the default agent in a dedicated terminal window — or brings up the picker if you haven't chosen yet. Right-click the agents icon on the top bar (once it appears) to launch the default agent from there as well.
You can also launch it straight into a task with omarchy agent prompt "Review this project". Agents launched this way run unattended in their respective don't-stop-to-ask modes, so be ready for them to actually do things. And since agents refuse to remember trust for your home directory, launches from $HOME start in ~/Work instead.
Use the shell shortcuts
There are terminal shortcuts too: a runs the default agent inline in the current terminal, while c, cx, and cy start OpenCode, Claude Code, and Codex directly (again in their auto-approving modes).
Theme changes sync to the agents as well: Claude Code, Pi, and OpenCode all follow along when you switch the Omarchy theme.
Wrap another CLI
To wrap an additional CLI the same way, run omarchy-mise-install <package> [command-name]. The stubs are kept current along with everything else mise manages when you run omarchy update (or the mup alias).
Check usage from the agents panel
The top bar grows an agents icon the first time Omarchy finds AI coding usage on the machine — and stays out of the way until then. The panel behind it tracks every subscription in one place: your plan, the percentage used of the 5-hour session and weekly limits (or the remaining prepaid balance), and token usage by day and by model. Claude Code, Codex, and Fireworks are covered out of the box.
Left-click the bar icon for the panel. The usage records behind it are regenerated every 15 minutes by omarchy agent usage-update, and the panel can even merge usage from your other machines via a synced folder. See the README under $OMARCHY_PATH/shell/plugins/agents/ for the full settings.
Hand crashes to the default agent
Omarchy watches systemd-coredump for process crashes. When something segfaults, you'll get a "Process crashed" notification — click it, and the crash is handed to your default agent along with Omarchy's diagnose-crash skill, which walks the agent through establishing the facts from the core dump and deciding whether the crash is worth reporting upstream. You can also run it by hand against any PID from coredumpctl list with omarchy agent crash <pid>.
The watching is on by default. Turn it off under Trigger > Toggle > Crash Capture (or with omarchy toggle crash-capture) and the notifications stop; omarchy agent crash <pid> still works by hand.
Crashes can also be silenced one program at a time, which is what the diagnosis offers you at the end:
omarchy crash mute hyprlandstops the notifications for that program onlyomarchy crash mute hyprland offbrings them backomarchy crash muteon its own lists what you've muted
It takes the binary's path as happily as its name, so omarchy crash mute /usr/bin/hyprland does the same thing. Quote a name with a space in it, as in omarchy crash mute 'Some App'. Everything else still notifies, and the muted program still crashes — this hides the reminder, it doesn't fix anything.
Treat the Omarchy skill as experimental
Agent skills help AI use specific tools in a specific way, and Omarchy ships with a default skill for tailoring the system: tweaking your Hyprland config, adjusting the bar, or even creating a new theme from scratch. It's symlinked into the skill directories for Claude Code (~/.claude/skills), Codex (~/.codex/skills), Pi (~/.pi/agent/skills), Antigravity (~/.gemini/config/skills), and the generic ~/.agents/skills location, so most harnesses pick it up automatically.
Treat this skill as experimental. Different models will use it to different effect. It's best to run in plan mode first, so you have an idea of what the agent would like to change. Then be ready to rollback changes or even invoke omarchy reinstall configs if the agent makes a mess of everything.
The Install > AI menu also carries a couple of graphical AI apps: the ChatGPT desktop app, and Grok Bot for chatting with xAI's models. Omarchy recommends LM Studio and Ollama for local LLM models; if you're new to local models, start with LM Studio. You can install either under Install > AI in the Omarchy Menu.
Next step: read the official AI chapter, pick a default with omarchy default agent <name> or Setup > Defaults > Agent, then launch it with Super + Shift + Ctrl + A. If you try the Omarchy skill, stay in plan mode first and keep omarchy reinstall configs handy.