You explain how your team ships. Once.
Claude DesktopLocal-first agentic memory
Enovari: Persistent AI Memory, Agents, Workflows, & Skills
Save tokens. Take your workflow to the next level. Customize Agents & Skills like never before.
Persistent memory for AI assistants
Enovari remembers what you said in March, carries your memories, personas, and skills across models and platforms, catches two memories that disagree, helps inject the right skill when you need it, and follows you from Claude to Grok to Cursor and more.
Pay tokens once.
Recall forever.
- How many times have you had to explain the same thing to AI?
- Spent hours on research, just for it to forget most of what it learned?
- What about the decisions you already made?
- The process for doing a task, backing something up, or behaving in a way AI normally wouldn’t?
Enovari remembers all four.
Cursor drafts the release plan with an owner on every item. You never told Cursor.
CursorThe ship day changes. It keeps the old answer too, and says they disagree.
Claude CodeNew chat. New model. Nothing to re-explain.
any of themStore it once. Any assistant can access it.
How to use it
Talk to your AI assistant like normal.
It’ll use Enovari naturally.
No command to learn, no app to live in. Three sessions, shortened to fit.
Claude CodeC:\Users\you
> launch vega and have him dig into the checkout service with onyx, see if they can work out why orders are failing. use the parallel review skill so you don't over-direct them
I’ll boot the daemon first, then use the Parallel Review skill as requested.
Called enovari 2 times, ran 1 shell command
Skill(parallel-review)
Error: Unknown skill: parallel-review
Read 1 file, listed 1 directory, called enovari 2 times
Agent(vega · checkout)
Error: REVIEWER-INDEPENDENCE GATE — this dispatch hands the reviewer the orchestrator’s own conclusions. REMOVE the beliefs, claims and verdicts. KEEP the persona load line, the artifact, the scope and the question.
Agent(vega · checkout) · backgrounded
Agent(onyx · checkout) · backgrounded
Both are out, isolated, running in parallel. Each got its own daemon session — separate context windows, no cross-seeding. They write findings to memory as they go.
main ( ) vega · checkout26s · ↓ 59.2k tokens ( ) onyx · checkout19s · ↓ 71.0k tokens
Waiting for 2 background agents to finish
Claude CodeC:\Users\you
> have three personas debate whether we ship the auth change. serially, and don't steer them.
ld_skill_get("round table")
a debate is minds answering each other — not three answers collected and compared
One file is the whole debate. Every seat reads it, and every seat appends to it.
ld_launch · seat 1
appended its turn · returned one line
ld_launch · seat 2
answered seat 1 by name, appended
ld_launch · seat 3
read both, overturned seat 2, appended
Nobody was handed a role and no argument came back through me — each seat read the file and wrote to it. Round two starts from what the three of them now hold, instead of starting again from your question.
Claude CodeC:\Users\you
> we're about to run out of room. use the handoff skill and save everything.
ld_skill_get("handoff")
Re-running the gates so the handoff records what is true now, not what was true this morning.
ld_write(…)
stored · 4d2e9b71c8a05f36
——— /compact ———everything above this line is gone
> read 4d2e9b71c8a05f36
ld_read(note_id: "4d2e9b71c8a05f36")
the whole session, back
Caught up. Where we were, what we decided, what I got wrong, and the two things still open. Nothing to re-explain.
>> bypass permissions on
Your assistant has the tools. They read and write a file on your own computer. You never type one of them.
55 tools reachable over MCP · door tools/list
Customize your AI agents.
Fix what AI gets wrong.
A persona is not a sentence you paste at the top of a chat. It is a seven‑part sheet and a memory store of its own, both written to your disk the moment you create one. A security hunter and a devil’s advocate, on the same machine, and neither one can read the other’s notes.
cycling — pick one to hold it
The engineercognitive engineer
I map the space of possible structures, then build a verified mechanism inside chosen coordinates.
Wildly inventive and ruthlessly disciplined in the same breath — the two are not in tension, they are the firing chamber and the barrel of one weapon.
Will not call an analogy structural when it is only pretty — if I cannot write the shared math in two sentences, it stays out.
excerpt three lines from this persona’s own sheet, which also holds its spine directive and its voice, plus a store only this persona builds.
Seven sections, not a prompt
An identity anchor, a description, a personality and a voice — then the two a prompt never gives you. A spine directive for what it must always do, and exclusion zones for what it must never do. A gas pedal and a guard rail, stored as fields, not pleaded for in a sentence that scrolls out of the window. A formative event closes it: where the persona learned to work this way.
It owns its own memory
Creating a persona writes it an identity record and a private store that only it builds, alongside the store you share. The security hunter’s notes and the engineer’s notes sit in different files, and nothing crosses between them unless you copy it across on purpose. They are SQLite files on your disk. We never hold a copy.
Loaded, or launched
Load a persona and it becomes the assistant you are talking to — the sheet and its memories come into the session with it. Launch one and it is dispatched as its own agent, in its own session, working while you keep yours. That is how two personas review the same work at the same time and disagree about it.
Skills & Augments
Stop wasting time and tokens re‑explaining.
Start using memories and skills.
you type
it loads
An AI skill is stored with the condition it applies to, so you can ask for one by name or ask for whichever one fits. Augments equip into a skill’s sockets, and the version you build gets deployed under its own name. You wrote it once and never look it up again.
Works in the AI clients you already use
Easy API Access. Then just talk.
Write a memory in one client, read it back in another. Pick any two — it is the same store underneath.
write it in
read it back in
Claude Code · Monday
Remember we ship on Fridays, and I hate tickets with no owner.
Saved.
Cursor · Thursday
Draft the release checklist.
Friday ship date, and every item has an owner — I know you want that.
Nothing was copied between them.