Skip to content

[Improvement] Default-agent abstraction: omacase agent + launch keybind + shell alias #22

Description

@splaice

Quattro feature

Omarchy 4 makes "your coding agent" a first-class default: omarchy default agent <name>, a dedicated launch keybind (Super+Shift+Ctrl+A opens the default agent in its own window), an a terminal alias for inline use, and omarchy agent prompt "<task>" to fire a task directly.

Omacase fit

Omacase ships four agent CLIs (claude, codex, opencode, grok) but no notion of the agent. All the machinery exists: the Ghostty overlay helpers in lib/wm.sh (_ghostty_popup_toggle), the managed zshrc for the alias, OmniWM for a keybind, and completions/menu patterns.

Proposed shape

  • omacase agent — show default + status; omacase agent default <name> persists to ~/.config/omacase/agent (seed-once user config, joins _backup_targets)
  • omacase agent launch — default agent in a centered Ghostty overlay (same pattern as omacase files); wire an OmniWM keybind through the user-owned settings
  • a alias in the managed dot_zshrc → the default agent inline
  • omacase agent prompt "<task>" — pass-through to the agent's one-shot mode where the CLI supports it (claude -p, codex exec, …) — capability table per agent
  • Completion, menu entry, doctor line (default resolves to an installed CLI)

Notes

This is the prerequisite for crash-capture-to-agent (separate issue). Usage tracking already exists (omacase usage).

🤖 Generated with Claude Code

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    improvementSystemic improvement for a future release — not a defectquattro-parityInspired by Omarchy 4 Quattro — evaluate for Omacase parity

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions