Support for adding custom coding agents (e.g. Antigravity CLI) to omarchy default agent

[Marchee72]

What's missing

omarchy-agent and omarchy-default-agent (part of the omarchy package itself, not user config) hardcode the list of supported coding agents:

pi | omp | opencode | claude | codex | grok | gemini | copilot | crush

There's no extension point to add a new agent. Installing one via AUR isn't enough to get it wired into Omarchy's agent tooling — none of these pick it up:

• omarchy default agent <name> (rejects anything not in the hardcoded list)
• The agent picker menu on Super+Shift+Ctrl+A
• The omarchy.agents bar widget (usage tracking has its own per-agent collector, omarchy-agent-usage-<agent>)

Since these live in pacman-owned files under the omarchy package, they can't be safely patched locally — any edit gets silently reverted by omarchy update.

Concrete case

Google shipped a CLI companion for Antigravity (antigravity-cli, AUR package, binary agy) as effectively a new generation of gemini-cli. There's currently no way to make it (or any other future agent) a first-class citizen in Omarchy's agent system — only a manual workaround: a personal Hyprland keybinding that reuses the org.omarchy.agent app-id to at least get the same floating-window treatment as built-in agents, with none of the picker/bar-widget integration.

Suggestion

Add a lightweight, user-writable extension point — e.g. a ~/.config/omarchy/agents/<name>.toml (or similar) that omarchy-agent/omarchy-default-agent read to register a custom agent's launch command, and that the picker menu and omarchy.agents widget could optionally surface too. Doesn't need full first-class support (icons, usage parsing, etc.) — just a way to plug an arbitrary agent binary into the existing launch/window-treatment machinery without touching packaged files.

Happy to help test this against a real-world case (Antigravity CLI) if useful.