🤖

Morpheus AI

Listening...
Backend unknown

Start

Morpheus Launchpad

One install, one run command, one connect pack for humans and agents.

Human start
  1. Install Morpheus
  2. Run backend and UI
  3. Click Prepare Agent
Agent start
  1. Fetch manifest
  2. Read WAKE.md
  3. Compile and verify after edits
Native Manifest
A2A Agent Card
MCP endpoint
Run Test MCP Tools to verify the local MCP endpoint.

              

              

Project Setup

Backend working directory

Context Sources

One path per line, relative to the project root. Use the workspace root and list several folders when Morpheus should absorb more than one project.

Load config to inspect watched paths.

Integration Paths

Load integration status for optional external context.

Model Smoke


              

Readiness

1
Backend Waiting for API
Check
2
Project Choose a root and initialize
Pending
3
State Compile to create WAKE.md
Pending
4
Receipt Verify after compile
Pending
5
Agent Bootstrap AGENTS.md
Pending

Next Action

Run diagnostics to load the next action.


              

Agent Connect

Waiting for backend


              

              

Agent Prompt


              

Agent Handoff

Build a complete copyable bundle for another agent.


              

AGENTS.md Preview

Preview not loaded


              

Diagnostics

Run diagnostics to inspect backend, project, WAKE, and receipt readiness.


              

FAQ

How do I connect Morpheus to a project?

Set Project root, keep Context Sources as . for the whole project, then click Prepare Agent. Morpheus initializes local state, compiles WAKE.md, verifies the receipt chain, and prepares AGENTS.md for other agents.

How do I include several folders or projects?

Choose a parent workspace as Project root and list each folder in Context Sources, one per line. Example: frontend, backend, docs. Morpheus keeps paths inside the selected root for safety.

What should another agent do?

Give the agent the Agent Connect URL or run morpheus prepare-agent. The manifest tells it the next action, where WAKE.md lives, and which commands must run before and after edits.

What is WAKE.md?

WAKE.md is the compiled project state: current decisions, tasks, notes, source references, and receipt metadata. Agents should read it before changing the project.

Should WAKE.md be committed?

Public repositories can commit a curated root WAKE.md as a showcase. Private workspaces should keep generated state inside .morpheus/ with morpheus wake . --private.

Is Morpheus a model trainer?

No. The default path is compile, cite evidence, hand off state, and verify receipts. Local adapter training is experimental and should only use reviewed, intentionally prepared datasets.

🤖
Hello. Connect the backend, set a project root, then run compile or verify from the sidebar.
just now
🤖

Project Status

0
Sources
0
Claims
0
Evidence

Last Compilation

Not compiled yet

Receipt Chain

No receipts

WAKE.md

Run "morpheus compile" to generate WAKE.md

Settings

Project Root

Backend working directory

Backend API

Integrations

No integration manifest loaded.

Voice

TTS: Silero | STT: Whisper