The Conductor

The Conductor is the right column of the desktop app and the heart of how Monday Morning works. It’s an AI orchestrator that reads the room across every session in the active project, captures what you want in plain English, decides whether that’s a quick task or a full spec, and launches it — then keeps surfacing what to pick up next.

If the old model was “open a chat and explain your project,” the Conductor flips it: the project state is already loaded, so you just say what you want.

What’s in the panel

From top to bottom, the Conductor is composed of:

Section	What it does
Header	A Brief button (runs `/mm:brief` for a contextual briefing) and a Project Settings button.
Roadmap pulse	A one-line read on the project’s roadmap when one exists, or a prompt to create one. Opens the full roadmap board in a modal.
Avatar & mood ring	A status avatar whose color (“mood ring”) reflects what the Conductor is doing, plus the active session count. Click it to open the Context browser (docs, specs, notes).
Harvest budget chip	A compact “hours left” chip — shown only when the Harvest plugin is enabled and the project is mapped to a Harvest project.
Active sessions	Live cards for every running / waiting session, sorted with running first. Click one to bring it into focus.
Ask	The natural-language input field (see below).
Inbox	Parked ideas plus AI suggested next picks.
Specs / Tasks	The to-do list: specs and quick tasks that are ready to build.
GitHub	Pull-request status for the project, pinned to the bottom.

Ask: turn plain English into running work

The Ask field is where you describe work. It has two modes and, in Code mode, two dispositions.

Code vs. Plan

Code — Describe a piece of work and the Conductor classifies it. It uses Claude to decide whether your request is a Task (a quick, single-session change), a Spec (a larger feature worth shaping first), or a Match to existing work — and shows you the verdict with its reasoning.
Plan — Describe a feature and the Conductor opens a planning session to shape it into a spec, skipping classification.

You can also type a /slash command directly (e.g. /mm:spec-start auth). An autocomplete drawer appears as you type /; navigate it with the arrow keys and select with Enter or Tab.

Start now vs. Park

In Code mode, a second toggle controls disposition:

Start now — Classify and launch immediately.
Park — Drop the request into the Inbox without classifying or starting anything. Frictionless capture for “later.”

The classification card

When you submit in Code/Start-now mode, the Conductor shows a Classifying… spinner, then a result card with the type (Task / Spec / Match), a suggested title, and its reasoning. It auto-launches after a 3-second countdown — press Launch to go now, or Cancel (or Esc) to back out. If something goes wrong, an error card offers a Retry.

Images and custom commands

You can paste or drag images into the Ask field to give Claude visual context (up to a per-message limit). If the project defines custom commands, they appear as one-click chips below the input and run with their configured working directory and environment, showing the result in a small toast.

Inbox: parked ideas and suggested next steps

The Inbox is your shelf of captured-but-not-started work:

Parked tasks — Everything you sent with Park. Search, start, view, or delete each one.
Suggested next — The Conductor picks from the parked pile and explains why it’s suggesting each one (e.g. it matches the file you have open, or relates to work that’s actively moving). Start a suggestion with one click, or dismiss it (the task stays parked).

Specs & Tasks: what’s ready to build

Below the Inbox, the Conductor lists the work that’s ready to go:

Specs — Ready-to-build specs (specd / backlog) that aren’t finished yet, each with a status badge, task progress, an ownership chip if a teammate owns it, and Start / View actions.
Tasks — In-progress and in-review quick tasks.

Starting a spec or task here dispatches it through the same front door as the Ask field — the Conductor reuses or creates a session and tells Claude to do the work.

Active sessions

The active-sessions list mirrors what’s live in the Session Rail, but scoped to the work the Conductor is driving — with progress and anything that needs your attention. Click any card to focus that session in the center pane.

Sessions & Terminals — the sessions the Conductor launches and tracks.
Desktop App Overview — the three-column shell.
Briefs (Context Recovery) — what the Brief button generates.
Specs & Workflow — how specs are shaped, built, and verified.