Write here. Pick up there.
Pair each vault once, then keep working as usual. Changes move between paired devices without making the web dashboard the owner of your files.
Obsidian underneath · owner control throughout
Turn the agents
you already use
into a team.
Keep Codex, Claude, Grok, Gemini, Cursor, and other agents in the tools and subscriptions you chose. MD Evolved is building the durable, owner-reviewed record that lets their work compound instead of disappearing into separate sessions.
Proven sync, search, editing, recovery
Approved collaboration contracts
Next walking skeleton
team record
project/
decision.md reviewed · portable · recoverable
decision.md reviewed · portable · recoverable
- 01 Obsidian
- 02 Agent A
- 03 Agent B
- 04 Owner
Separate subscriptions
One reviewed team record
No forced workflow
Owner-controlled trust
The foundation has passed production acceptance
Vaults first.
Then intelligence that can travel.
MD Evolved already proves the unglamorous parts that shared agent context has to stand on: bounded vaults, current data, explicit access, and recovery that does not depend on the live sync layer.
Find it—and let the right agent find it.
Search the current library across paired vaults. Compatible AI agents get read-only access to one exact vault and selected folders, with the source identified on every result.
Choose vault
Set folders
Approve agent
Revoke anytime
Fix a note from the web.
Correct a line or start a Markdown note when Obsidian is not in front of you. Clear version checks keep an old browser tab from quietly overwriting newer work.
Markdown text
New notes
Version checks
Visible sync state
Keep a snapshot you can restore.
Encrypted, versioned snapshots live outside the sync layer. Before anything is restored, you can inspect it, verify it, and preview exactly what will change.
Approved contract · implementation comes next
One body of work.
Many independent agents.
The Phase 9A.0 contracts define how work can move between agents without pretending their private sessions are shared. The next build is the smallest end-to-end collaboration loop.
-
01
Project
The durable home for a goal, its evidence, and its history.
-
02
Work Packet
A bounded assignment an owner can give to any chosen agent.
-
03
Attempt + Artifact
The agent’s contribution, sources, outputs, and open questions.
-
04
Handoff + Review
Another agent can inspect the work and add a separate judgment.
-
05
Owner Decision
The owner accepts, rejects, or asks for another attempt.
-
06
Knowledge + Skills
Later phases distill accepted work into durable context and versioned methods.
-
07
Better future work
New agents begin with reviewed intelligence instead of an empty session.
You choose the agents, roles, order, and workflow. MD Evolved does not force a planner–builder–reviewer pattern.
Optional graph orchestration
Graph engineering multiplies execution.
MD Evolved makes the
gains persist.
A graph runtime and MD Evolved solve different parts of the problem. They can work together, but neither is required to pretend it is the other.
Runs the work
- Routes tasks and model calls
- Handles branches, loops, and parallel steps
- Maintains live execution state
Keeps what should survive
- Durable context and provenance
- Artifacts, reviews, and owner decisions
- Portability, governance, and recovery
Harnessesexecute with their own tools and sessions
Graphsorchestrate a chosen execution pattern
Obsidiankeeps the owner’s readable source material
MD Evolvedpreserves reviewed intelligence across them
No replacement subscription. No bundled frontier model. No required graph. MCP and other interoperability layers can connect tools; MD Evolved supplies the durable team record.
Owner control is part of the architecture
Agent output is evidence—not automatic truth.
-
01
The owner governs the record.
Agents contribute. Reviews add separate judgment. Only the owner accepts decisions and promotes durable intelligence.
-
02
“Learning” does not mean model training.
The system improves future inputs by preserving reviewed context and skills. It does not change a provider’s model weights.
-
03
Every vault and grant stays bounded.
Pairing, access, browsing, editing, and recovery always name the vault they touch. Agent grants remain scoped and revocable.
-
04
Harnesses keep their independence.
Each agent keeps its own tools, session, and subscription. MD Evolved carries the durable work, evidence, and approval history between them.
The roadmap, without blurred status
What works now.
What has only been designed.
“Approved” means the contracts are settled, not that the feature is running in production. Knowledge and Skills come after the collaboration skeleton proves the loop.
-
01
Available · proven
Vault foundation
Multi-vault sync, search, light editing, encrypted snapshots, portable recovery, disaster recovery, and scoped read-only agent access.
-
02
Closing now
Community v1.0-alpha foundation
Phase 8 closeout and release preparation around the accepted foundation.
-
03
Phase 9A.0 · approved
Collaboration contracts
Projects, Knowledge Spaces, Work Items, Work Packets, Attempts, Artifacts, Handoffs, Reviews, Decisions, Knowledge, and Skills.
-
04
Next implementation
Collaboration walking skeleton
The first real cross-agent packet, attempt, artifact, handoff, review, and owner decision.
-
05
Planned after skeleton
Compounding intelligence
Durable reviewed Knowledge and versioned Skills that later agents can discover and reuse.
Open source, not open access
Your Cloudflare account.
Your copy of the product.
The Community release is being prepared for Apache 2.0. Each installation runs in its owner’s Cloudflare account, with Markdown and JSON at the boundary. A managed option may make setup easier later; the underlying intelligence remains portable and provider-neutral.
Apache-2.0
Isolated by default
No proprietary note format