Evolved

Private alpha · one project record across your AI tools

Make one AI’s work the next AI’s head start.

The AI tools you subscribe to are good at different things. OWD carries the work you choose to share from one compatible client to the next, with its sources and your decisions attached. You choose every handoff, so the next agent starts further ahead.

Open OWD Platform on GitHub See how the work adds up

Private alpha. GitHub access is invitation-only and will show a 404 until you’re invited. OWD doesn’t choose or run agents; you control every handoff.

Use the tools you prefer Carry approved work forward Choose every handoff
project record project/
handoff.md cited · reviewed · yours
  • 01 Sources
  • 02 AI tool A
  • 03 AI tool B
  • 04 You decide
Keep the AI tools you already use You pass selected work between them You control every handoff Each session starts further ahead

Why the work adds up

Your AI tools don’t need to share a brain. They need to share the work.

OWD keeps the project record between sessions. You decide what goes into it, which authorized client sees it, and what the next job starts with.

  1. 01

    Use each tool where it shines.

    Choose one AI tool for research and another for implementation or review. You decide the lineup and order.

  2. 02

    Keep the work worth keeping.

    OWD keeps the submitted result with its sources and open questions instead of leaving it stranded in one session.

  3. 03

    Give the next agent a head start.

    Give another authorized client a focused assignment drawn from that record. It receives only the scope and records you authorized.

  4. 04

    You decide what carries forward.

    Accept the work, reject it, or ask for another attempt. You record the final decision, and future handoffs can carry it forward.

OWD doesn’t choose or run agents. You choose each tool, every handoff, and what context moves forward.

Get OWD on GitHub

Build one project history across the AI tools you use.

OWD Platform lets separately authorized clients submit and retrieve the work you choose to share. OWD Sync ties that record to the Obsidian vaults you choose. Both are Apache-2.0 projects, and Platform access is limited to invited alpha testers for now.

OWD PLATFORM Private alpha

OWD Platform

OWD Platform combines an owner-controlled web app, a Cloudflare backend, and a project record. Authorized clients submit and retrieve cited work through OWD under your direction.

  • Deploys to your Cloudflare account
  • Separate authorization for each client
  • Cited handoffs, reviews, and owner decisions
  • Encrypted snapshots you can inspect and restore
Open OWD Platform Invitation required
OWD SYNC Public repository

OWD Sync

The Apache-2.0 Obsidian companion that pairs a selected vault with your OWD Platform installation.

  • Vault-specific pairing
  • In-app setup
  • Version-matched releases
View OWD Sync Browse releases
Apache-2.0 Single owner Your Cloudflare account Exportable data

Built around the vaults you own

Your notes stay yours. You choose what each client can read.

Sharing context helps only when you know where it came from and who can see it. OWD keeps vaults separate, shows exactly what each client can read, checks that a note is current before saving, and keeps backup data in formats you can take with you.

01 / SYNC

Write here. Pick up there.

Pair a vault on each device and keep working in Obsidian. OWD syncs changes between paired devices; your vaults remain your files.

02 / FIND + CONNECT

Find a note. Share only what you choose.

Search across your paired vaults. Each authorized MCP connection can read only the vault and folders you grant. Every result names its source.

Choose a vault Choose folders Authorize a client Revoke access
03 / EDIT

Fix a note from the web.

Edit a line or create a Markdown note when Obsidian is not open. OWD checks that the note has not changed before saving, so an old browser tab cannot overwrite newer work.

Markdown text New notes Version checks Visible sync state
04 / RECOVER

See what a restore will change.

Snapshots are encrypted, versioned, and stored separately from the sync layer. You can inspect every change before applying one.

The trust model

Agents contribute. You decide what counts.

  1. 01

    One owner governs the record.

    Agents can contribute and review work, but only the owner can accept a decision into the project record. The private alpha supports one owner, not teams or shared administration.

  2. 02

    Saved context is not model training.

    OWD helps future sessions by saving cited handoffs, reviews, and accepted decisions. It does not train or change any provider’s model.

  3. 03

    Access stays tied to a vault.

    Every pairing, grant, edit, and restore names the vault it affects. Revoking a grant blocks future OWD requests; it cannot erase information a client already received.

  4. 04

    Your AI tools stay independent.

    Each client keeps its own tools, session, and subscription. OWD does not ingest hidden conversations or provider credentials; it keeps owner-shared project records instead.

Current testing limits

What to know before you test it.

Scoped access is production-tested, and the two-client handoff has passed internal validation. The private alpha exists to prove that handoff with an invited owner and two separately authorized clients. Keep these limits in mind while testing:

01 / OWNER

One owner. Test data only.

The alpha supports one owner. Use disposable synthetic notes; do not connect personal or production vaults yet. Team accounts and shared ownership are not supported.

02 / CONTENT

Markdown text only for now.

The web app can create and edit Markdown text. It cannot rename or delete files, write attachments, or make arbitrary changes under .obsidian. Snapshots currently exclude attachments and .obsidian files.

03 / CLIENTS

Support is based on what we have tested.

We have used scoped, read-only access with a generic MCP client, MCP Inspector, Codex, Claude Code, and Grok Build. That does not mean every client has passed the full collaboration test.

04 / EGRESS

Revocation blocks future calls.

OWD checks the grant on every request. Revoking it blocks future requests, but cannot erase text already sent to a client or control what that client or its provider does with it.

CLOUDFLARE COST Usage is billed to your account.

Small tests may stay within Cloudflare’s included allowances, but OWD cannot promise that it will cost nothing. Request, storage, and snapshot costs grow with your usage.

Review Cloudflare pricing

Private alpha on GitHub

Keep the AI tools you like. Make their work add up.

Open OWD Platform

Invitation required for now. We’ll open the repository and add one-click Cloudflare deployment after the remaining release checks.