The desktop app
The desktop is agent-first
The desktop app carries MUON's local brain and runner — there is nothing else to start. The layout puts your agents first: a slim rail on the left, a grid of agent panes in the centre, and an inspector drawer on the right. Open it once past Gatekeeper (see Install) and sign in, then connect an agent.
The icon rail
An icon rail runs down the left edge, labelled “Workspace navigation.” Each destination has an icon, a tooltip, and a selected state, grouped into Work, Crew, Knowledge, Ops and Settings. The same destinations are reachable from the ⌘K command palette.
| Group | Destinations |
|---|---|
| Work | Mission, Attention, Issues, Control |
| Crew | Crew, Topology |
| Knowledge | Memory, Graph, Context, Evidence |
| Ops | Governance, Cost, Timeline; Observability when certified |
| Settings | Settings |
Under each mission, a row lists its running and queued agents with a vendor icon, a plain-text activity line, elapsed time, and a gate dot. Clicking a row opens that exact agent. A badge on Control counts pending decisions, and a dot on Crew marks active crew work.
The workspace grid
Selecting an agent turns the centre into a grid of up to four panes. Each pane shows the vendor, task title, agent name, elapsed time and current activity. The mission chat stays full height; agent panes are for the crew working on that mission.
- Clicking an agent tab focuses its pane; at four panes, the new one replaces the least-recently-focused.
- Split controls on each pane header divide it horizontally or vertically.
- Switch tabs or rearrange panes while keeping a takeover terminal open.
- The input box on a governed agent's pane is disabled and reads “Input is disabled for a governed agent” — a dispatched agent runs its brief; you steer it through take-over, not the pane.
The inspector drawer
The inspector drawer opens on the right for the focused pane. Toggle it with ⌘I; Escape closes it. It is closed by default, and its open state, section and width persist. It has seven sections:
- Overview, Timeline, Changes, Tools, Capabilities, Commands and Audit.
Start a mission from a GitHub issue
The Issues destination lists issues from a GitHub repository you have connected. It has a project picker, an Open / Assigned to me / All control, and a query bar (is:, assignee:@me, label:"x"); an unsupported token shows a hint and is never sent. Issue rows show the title, labels and assignees.
“Start mission →” opens a new chat whose composer is pre-filled with the issue marked as untrusted context, with the note “Pre-filled from issue #N. Review it, then press Send.” Review and edit the draft before pressing Send. If GitHub is not connected, use Open Setup. If access is missing, check your repository permissions on GitHub.
GitHub access is read through your own sign-in
The Issues view reads through MUON's existing GitHub connection. It lists issues only (never pull requests) and never widens access on its own. Connect or disconnect GitHub in Settings → GitHub.
Where approvals appear
When an agent's work crosses a gate, a compact decision row appears on that agent's pane and the Control badge on the rail increments. A merge gate opens the full review. A gate covered by Full-Auto shows that coverage. The bottom status bar shows brain health, per-vendor quota chips, running agents, and pending gates that still need you; opening Control takes you to the full approvals queue. For what each gate means, see Governance.
First launch
- 01
Open the app past Gatekeeper
The v1 build is unsigned, so macOS blocks the first launch. Use System Settings → Privacy & Security → “Open Anyway”. The Install page has the full walkthrough.
- 02
Sign in
The app authorizes this install through your account. A distributed install stays locked until it does.
- 03
Connect your first agent
Log in to a coding agent with its own CLI, then let MUON register its MCP server. The Quickstart walks through connecting an agent and running your first mission.