Project memory and Dreaming — how Euclis keeps context current
What Euclis project memory is, how Dreaming maintains it while you're away, and why humans and AI agents share one brief.
Most teams lose context in chat scrollback. New teammates ask the same questions. New AI sessions start from zero. Euclis is shared project memory — decisions, blockers, and milestones captured where work already happens, then kept current.
Capture from every surface
Euclis listens on WhatsApp, Claude, Cursor, and the web. You do not re-enter the same decision into a wiki. Capture records the moment; the workspace turns it into structured memory.
What gets stored
- Decisions — what you chose and why
- Blockers — what is stuck and who it affects
- Dependencies — what waits on what
- Milestones — shipped moments worth keeping
What Dreaming does
Capture only ever sees one moment. On a schedule, Dreaming steps back and tends the whole store:
- Consolidate — merge duplicate notes
- Reconcile — flag or resolve contradictions
- Surface — highlight patterns no single note could see
- Prune — file away what has gone stale
Nothing is deleted. Plan retention may hide older events from recall — they stay in the store. Hobby includes raw capture; Team adds curated Dreaming (dedupe, contradiction resolution, insights).
One brief for humans and agents
Teammates read memory in the app. Coding agents call get_project_contextover MCP and load the same brief — so Claude Code or Cursor does not need you to paste last week's chat.
Still a board when you need one
Euclis includes kanban, discussions, whiteboard, and assets. The difference is the center of gravity: memory first, tasks as part of the same workspace — not another empty board you forget to update.
Start free on Hobby or see pricing for Team curated memory.