Architect
Frames the problem, drafts the plan, lists risks and approvals before the work begins.
Operator → Agents
Specialists, not one assistant.
One Operator, several specialists. The right one takes the turn, hands off when the shape of the work changes, and keeps the same thread open the whole time.
Screenshot needed
Ideally a 4-5s loop: Operator panel showing Architect finishing a plan → handoff arrow to Coder → Coder picks up and starts editing. Static fallback works too: panel with active specialist (Architect) highlighted and the next-up roster (Coder, Project, Reviewer) listed below.
/shots/operator-agents.pngRoster
Built-in specialists
Each one is a real agent with its own model mix, tool set, and behavior — not a different system prompt.
Coder
Picks up the plan, edits real files, runs tools, and ships the change inside the Space.
Project
Carries the release thread — tasks, schedules, follow-up, and who owns what.
Researcher
Reads documents, the web, and your data. Returns sourced answers, not vibes.
Reviewer
Double-checks output before success is reported. Catches the mistakes the first agent made.
Specialist (dynamic)
When a tool keeps failing, Morpheus spawns a specialist for that tool and verifies it works.