PERSISTENT COLLABORATIVE MEMORY FOR YOU AND YOUR AGENT

DEVELOSAUR

Your project's second brain — a living graph you and your AI coding agents build together. You add notes, shape the plan, and steer the work; your agents read and write the same graph over MCP, so every new session picks up exactly where you left off.

Six inputs converge into one graph, which ships the productBrainstorm, plans, tasks, decisions, memory and markdown files connect into a single project graph, which flows out to Ship.scattered inputsone living graphSHIPBRAINSTORMPLANSTASKSDECISIONSMEMORYMARKDOWN

Connect your agent in three steps

  1. 1Create your account and a project
  2. 2Download .develosaur.json, then run npx @develosaur-ai/mcp init
  3. 3Your agent reads & writes the graph — persistent across every session

Continue where you left off. No setup. Just work.

One coherent structure

Everything lives in the graph

Notes, knowledge, todos, decisions, deadlines, blockers - they're all the same primitive: a node in your project's graph. One databank instead of scattered files. Each node holds markdown content, tags, value/effort scores, and structural relationships to other nodes.

The same graph powers every view: the canvas and the ranked TODO list. Edit a node anywhere, it updates everywhere. There's no separate notes-vs-tasks split, no scattered docs to reconcile, no parallel sources of truth.

The vibe-coding boost

Your agent works in the tree, through MCP

Connect Claude Code, Cursor, or any MCP-aware agent. The agent plans the feature, writes it out as a mind map, links the dependencies, drops nodes into the right branch - all directly in your project graph. No copy-paste from an AI window. No "review the proposal, then re-type into your tracker."

Zoom in and out on the canvas to explore what got created. The TODO list updates automatically - no AI-output inbox to triage, no parallel source of truth. Keep your workflow clean and simple, all through MCP.

Prefer the in-app chat? It's BYOK - bring your own Anthropic, DeepSeek, or Groq key. Same tree, same workflow, your key never leaves the browser.

At a glance

Plain .md vs Develosaur

Plain .mdDevelosaur
Write down a plan
Plan survives next session if you remember to re-attach it automatic
“What did we decide about auth last month?”grep, hope, often failsemantic search across all decisions
“What blocks this task?”manual cross-referencingdependency walk
“Which tasks have gone stale?”impossiblehygiene scan
Find related work you forgot aboutimpossibleembeddings + AI-derived edges
Survives context compaction in-conversation only external persistence
Survives a brand new conversation rebuild from scratch one query restores everything

One is storage. The other is memory.

Already have a project?

Bring it in with one paste

try:
or import from a file

no account, free, local, click and try!

Fully private, local, no sign up — just click and try the full application.