MDevolved

AI coding tools are excellent at doing the work in front of them. They are bad at inheriting the work that happened somewhere else.

The plan is in Claude. The useful failure is in Codex. The decision is buried in a chat that expires. The next agent starts over, repeats the same mistakes, and asks the human to reconstruct the project again.

MDevolved makes the project—not the session—the durable unit of work.

It keeps the objective, current state, decisions, cited evidence, useful failures, preferences, attached skills, and exact next action ready for whichever authorized agent works next.

The lovable moment

You work on a project in Codex today. Tomorrow you open Claude—or a fresh Codex task on another computer—and say:

MDevolved resume project

The agent receives the current objective, accepted decisions, relevant cited evidence, known failures, working preferences, and the next action. It does not need the old chat. You do not rebuild the prompt.

When the agent finishes, it leaves a compact verified checkpoint. The next session starts further ahead.

That same loop works when an orchestration manages several agents: the harness still schedules and supervises them, while MDevolved keeps the shared Project truth, bounded context, evidence, review, exceptions, and continuity.

Fewer resets. Better handoffs. Work that compounds.

Related MCP server: Soul

Use the agents you already like

MDevolved is not another model, IDE, or orchestration runtime. Codex, Claude, Cursor, Hermes, Orca, and other compatible tools keep their own models, shells, sandboxes, worktrees, retries, and subscriptions.

MDevolved sits underneath them as the durable Project layer:

Markdown folder or Obsidian
            ↓
   owner-controlled Project
            ↓
memory · evidence · decisions · skills · next action
            ↓
one agent · another agent · an orchestration · another computer

Clients connect in the simplest shape they support:

• Direct MCP for compatible desktop, IDE, and terminal agents.

• Lead-mediated MCP when an orchestration keeps one authorized connection and manages its own workers.

• Portable Markdown/JSON handoff when live remote MCP is unavailable.

No provider becomes a required dependency. See the compatibility guide for the current protocol and dated client evidence.

How it works

1. Connect one Source. Connect the Markdown folder or Obsidian workspace you choose.

2. Connect an agent. Choose the agent, Project name, Source, and exact folders it may read. Revoke access at any time.

3. Say Connect this project to MDevolved. The agent creates, joins, or resumes the Project without a copied prompt or manual Project ID.

4. Keep working normally. The agent retrieves targeted evidence when needed and checkpoints verified progress before it finishes.

The ordinary agent loop is intentionally small:

resume → find what matters → do the work → checkpoint → continue

MDevolved handles routine context renewal and continuity. The owner returns only when work requests more authority, a destructive action, protected paths, more budget, or a decision between conflicting evidence.

Memory that earns its place

MDevolved does not scrape chats or turn every agent sentence into permanent memory.

• Evidence stays attached. Durable claims retain their sources and provenance.

• Suggestions are reviewable. Repeated preferences and successful methods can become proposed memory; they are not silently promoted.

• Skills stay portable and inert. A compatible harness may load them, but a skill cannot expand its own authority.

• Different roles get different context. Focused agents can continue prior work, independent agents can avoid peer conclusions, and synthesis agents can compare attributable results.

• Useful failures survive. A failed verification keeps the same work active instead of pretending the project advanced.

MDevolved derives one next action from that durable state, so the next agent starts with a useful move instead of another archaeology session.

Autonomy without another supervisor

Run one agent or an entire orchestration. MDevolved automates the routine coordination. It does not compete with the harness.

• A solo agent can complete bounded work under an owner-consented verification policy.

• A lead-managed run can delegate to several claimed actors and route an independent review.

• Routine allowed work continues without repeated MDevolved-specific owner actions.

• Authority expansion, destructive requests, protected paths, exhausted budgets, and conflicting evidence become explicit exceptions.

• Revocation is authoritative and immediate.

MDevolved records bounded results and evidence. It never claims to execute the agent's tests, ingest hidden reasoning, or control the agent runtime.

Own the memory

The complete Apache-2.0 Community source is public and deploys into your own Cloudflare account.

• Your files stay yours. Pair only the Sources you choose.

• Passkey-protected owner control. Every agent receives a distinct, revocable authorization.

• No raw transcript ingestion. MDevolved stores durable contributions, not provider conversations or chain-of-thought.

• Encrypted recovery. Snapshots are owner-key-controlled and independently restorable.

• Recovery restores knowledge, not power. Grants, credentials, sessions, actors, leases, and OAuth state never come back from a backup.

• No managed-service lock-in. Community remains independently deployable.

Read the full security model and backup and recovery model.

Start with a folder

The fastest generic Source path is one command:

npx mdevolved@latest sync .

Prefer Obsidian? Use the optional MDevolved Sync for Obsidian adapter instead. Both use the same source-neutral sync and durable Project model; Obsidian is an optional richer adapter, not a requirement. The canonical MD9 plugin identity is mdevolved-sync; the previously published owd-sync adapter remains available as a clearly labelled compatibility path while the canonical prerelease completes Community Plugins review.

Deploy Community

The deployment runs in your Cloudflare account. MDevolved never receives your Cloudflare credentials or recovery private key.

Six actions to your first durable resume

1. Deploy or open MDevolved. Deploy Community into your Cloudflare account, or open the MDevolved workspace you were invited to.

2. Claim it with a passkey. Create the owner passkey that controls Sources, agents, recovery, and revocation.

3. Connect one disposable Markdown folder. In that test folder, run npx mdevolved@latest sync . and approve only that Source.

4. Authorize one compatible agent. Approve its exact Source and folder boundary. You can revoke it at any time.

5. Connect the Project. In that agent, say Connect this project to MDevolved and keep working normally.

6. Resume in a fresh session. Open a fresh authorized session, say MDevolved resume project, and verify that the objective, evidence, useful failure, and next action return.

Watch the 25-second product demonstration, then use the agent-first quick start for client recipes and technical details.

Public alpha

MDevolved is ready for technical alpha testing, not yet for unattended use with irreplaceable data.

• Start with synthetic or disposable Sources.

• One owner per deployment; team accounts are not available yet.

• The managed service remains invitation-only.

• Web editing currently covers Markdown text and note creation—not rename, deletion, attachments, or arbitrary .obsidian writes.

• MDevolved Sync for Obsidian is not yet listed in Obsidian Community Plugins.

• Protocol compatibility does not imply that every client release has completed a dated live acceptance exercise.

See the current alpha status and public roadmap.

Learn more

• Why MDevolved exists

• Agent-first quick start

• Agent access and MCP

• Architecture

• Security model

• Complete documentation index

MDevolved was formerly called OWD. New installs, package imports, MCP operations, pairing links, portable formats, and the Obsidian adapter use the MDevolved identity. Existing deployments, stored records, bookmarks, old MCP operations, owd-pair links, exports, backups, and the owd-sync plugin identity remain readable through a compatibility adapter. The private former workspace package scope remains only in repository history and explicit compatibility fixtures; it was never a public package contract. Those technical names stay visible only where an existing client or stored record requires them; no rename or restore operation copies grants, sessions, credentials, or other live authority. The technical compatibility protocol retains the OWD name where changing it would break an existing client or durable record.

pnpm install
pnpm check
pnpm test
pnpm test:e2e
pnpm build
pnpm deploy:dry-run

See the development contract and public quality gates.

License

MDevolved is licensed under the Apache License 2.0. Vendored upstream components retain their original notices and licenses.