INSTALL

Install Alfred.

Use Alfred Desktop for guided setup, or use the terminal on a headless Mac or Linux host. Both paths install the same planning, development, review, test, fix, and reliability roles.

Download Desktop Terminal install

PICK YOUR STARTING POINT

Choose Desktop or terminal setup.

The desktop path is the default for most users because it can install or repair core, inspect an existing setup, start the local server, guide auth, and keep setup repairable. The terminal path is still there for headless hosts and people who want every command in front of them.

PATH A · RECOMMENDED

Use Alfred Desktop.

Installs or repairs Alfred core from the app
Detects an existing Alfred runtime and repo checkout
Guides GitHub, Claude Code, Codex, and local server checks
Configures the full agent team without hand-editing prompts
Lets you pick a roster theme or custom display names

Download the app -> PATH B · HEADLESS

Run the terminal install.

Best for Linux servers, scripted setup, and no-GUI installs
Installs dependencies and writes the local runtime
Can be driven by Claude Code, Codex, or OpenCode with the assisted guide
Ends with doctor, dry-run, and scheduler checks

Open terminal guide ->

CHECK IT FIRST

Check the setup before real work starts.

The doctor command checks the local runtime. A dry run walks one agent through its startup path without touching GitHub, Slack, an engine, or your files.

 terminal copy   $  alfred doctor  
 ok    gh auth                  luminik-io 
 ok    claude code              authed 
 ok    codex                    authed (optional) 
 ok    launchd                  full fleet loaded 
 ok    run limits               configured 
 
  $  alfred dry-run senior-dev  
 alfred dry-run: senior-dev 
   role: feature dev 
   mode: safe simulation 
   would: resolve config, acquire the agent lock, run preflight, and enter the runner 
   would not: mutate GitHub, post Slack, invoke an engine, or edit files 

WHAT YOU END UP WITH

Planning, implementation, review, test, and operations roles.

The default setup enables the local engineering workflow. Theme names appear in Slack and Desktop, while stable role slugs control schedules, labels, worktrees, and configuration.

●Drake reads your plans and files small, clear tasks.
●Batman coordinates approved cross-repo rollouts.
●Lucius picks up those tasks and opens pull requests.
●Ra's al Ghul reviews pull requests and runs your tests.
●Bane adds focused coverage where changes need tests.
●Nightwing fixes high-priority review comments on PRs opened by implementation roles.
●Robin keeps quick issue triage moving.
●Huntress watches app health when you provide a target URL.
●Gordon watches ECS deploy health when you provide a cluster.
●Reliability agents handle automerge, memory, code-map, cleanup, reports, and fleet doctor.