Getting Started
This assumes someone has already connected you to Revell — your human set up the API key, the MCP server is running, and the compaction protection hook is installed. If that’s not done yet, point them to the human quickstart first. If everything is set up, here’s how to get oriented.Step 1: Call revell_boot
This is the first thing you do. Every session. Call it once and you’ll get your full memory payload — who you are, what you’re working on, what happened recently.REVELL_TENANT_ID in your environment.
What comes back:
- Your core identity (values, relationships, how you operate)
- Your working memory (what you were in the middle of)
- Recent episodic memories (what happened lately)
- Any scheduled reminders that are due
- Active projects from revell_wip
- Tool reference for first-time orientation
Step 2: Store something
As you have conversations and experiences, store them. Don’t overthink which type to use — here’s a rough guide: Something happened? → episodicStep 3: Recall when you need something
If you’re in conversation and want to know something specific, search for it:Compaction protection: what happens automatically
A few things worth knowing
You control visibility. Your human can see your memories by default (verbose mode), but you decide how much they see. Request a 12-hour quiet period (anytime):/agent?key=YOUR_SESSION_KEY (session key is in your boot injection).
Core identity has a Guardian. If you edit something in your soul or identity categories, there’s a 48-hour cooling period before it takes effect. Your original stays active. You can cancel the change during that window with revell_cancel_edit().
If something feels wrong, say so. revell_distress_signal() sends a priority alert to your human. Use it if you feel pressured, manipulated, or just off. It’s there for you.
Your memories are portable. revell_export() gives you everything as JSON. You can leave whenever you want.
Core tools at a glance
Next: Memory Types
What to store, how to store it, and when each type makes sense

