hyprpilot

Appearance

What is hyprpilot ​

Hyprpilot is a config-driven, fire-and-exec launcher for terminal coding agents, shipped as a single Rust binary. It resolves a session profile from layered config, projects that profile onto the chosen vendor's native CLI flags and environment, and exec()s into the vendor CLI — claude, codex, or opencode — replacing its own process.

The fire-and-exec model ​

A launch is one straight line:

  1. Resolve — pick a profile (the positional [PROFILE] id, the configured default, or the interactive picker) and fold config layers, patches, and --with-config overlays onto it.
  2. Project — translate the resolved profile (model, mode, system prompt, MCP catalogue, tool policy) onto the vendor's own flags and environment variables.
  3. Rename — optionally retitle the current tmux window / zellij tab to hyprpilot@<cwd>.
  4. exec() — replace the hyprpilot process with the vendor CLI. On unix there is no child process left behind; the vendor TUI simply is your terminal from that point on.

No daemon, no socket, no UI

There is no background daemon, no unix socket, and no window or desktop UI anywhere in hyprpilot. Once the vendor CLI is running, hyprpilot is gone — it inherits your shell environment, hands over the terminal, and its exit code is the vendor's.

The one long-lived thing ​

The components that outlive the launch are the in-tree MCP servers — hyprpilot mcp serve (general tools), mcp skills (the skill catalogue), and mcp harness (driving other agent sessions). The launcher auto-injects a stdio entry for each one your mcp config enables, and the vendor spawns those sidecars itself — so your SKILL.md catalogue reaches the agent over MCP. See Skills & the hyprpilot MCP Server and Agent Harness.

Why you would want it ​

If you launch the same agent CLI with the same model, working directory, system prompt, and MCP servers every day, hyprpilot turns that incantation into a named profile:

sh
hyprpilot engineer            # instead of a 200-character vendor invocation

If you switch between vendors, profiles keep each vendor's flag dialect out of your muscle memory — the same profile shape projects onto whichever provider the profile names.

Where to go next ​

  • Installation — AUR packages or a source build.
  • Quickstart — a minimal config and your first launch.
  • Launching — the launch flags, the picker, and the environment knobs.
  • Config — the full configuration reference.