Four parts: a generated Soul.md, an MCP server, a Chrome extension, and a nine-phase conversation engine.
Daemon is a personal intent engine. It generates a Soul.md, serves an MCP server, puts a Chrome extension in the browser, and runs its conversation in nine phases.
v0.1 is launched. v0.2 is planned as a presence builder for thin digital footprints — the case where there is barely anything online to read you from.
The next action is written as a fork rather than a plan: build v0.2, or shelve the whole thing until Creator Codex needs it. Both branches are live.
It is not the only personal-agent build parked on this stack, and it doesn't pretend to be — a soul file and a long conversation about who you are show up under other names a few ranks away. Daemon's claim is the shipped one: v0.1 exists and launched.
Its claim on the future is thinner. The engine survives if something downstream wants what it generates; that is what the fork in the next action is asking.
One file, one server, one extension, one conversation.
Soul.md
Generated by the engine — the artifact the rest of it produces, and the thing at the centre of the hero above.
MCP server
The engine exposed as tools a model client can call, rather than an app you have to visit.
Chrome extension
The part that lives in the browser, where the footprint it reads from already is.
Nine-phase conversation
The engine runs in nine phases, in order. Nine is the file's number, not a flourish — the hero is that loop.
One version out, one version pending a decision.
Built in the Daemon repo on Next.js and Supabase. v0.1 launched; v0.2 is planned and not started. Status here is backburner.
The status was logged as a best guess — it is still to be confirmed at review zero.