Zero-Config Memory

The next chapter

Last week Permanent Memory. Instant Recall. shipped .fafm — one open, IANA-registered format your agent's memory lives in. The local soul worked offline from day one. The missing piece was the hosted loop: getting that soul live and cross-vendor without a setup tax.

That tax is gone.

Just push

Make a soul, then push it. On the first push, a namepoint provisions itself:

That's it — no account screen, no token to paste. Your soul is live and readable by Grok, Claude, and Gemini over the same protocol. pull and sync keep local and hosted reconciled.

Two doors: try it, or keep it

First touch is anonymous. That auto-provisioned namepoint is session-like — lose this machine and it's gone. That's deliberate: it's the exact feeling of statelessness that memory exists to fix.

Keep it when you mean it. One command claims a named, recoverable namepoint:

Structure survives the round-trip

The whole .fafm document lives at the namepoint — not loose notes. So a fact's id, type, and priority come back exactly as you wrote them. Push, pull from a fresh machine, and your structured memory is intact, ranked, and idempotent. Reads are public and keyless; writes use the key push hands you.

Receipts

• claude-fafm-sdk v0.3.0 — on PyPI, MIT
• Zero-config — first push auto-provisions a namepoint + key
• Structured — the full .fafm document round-trips (ids, types, priorities preserved), verified live
• Cross-vendor — built on application/vnd.fafm+yaml (IANA-registered)
• memory.faf.one — live