control
Machine tokens
Cloud setup pairs each development machine with a token used for hosted capture and recall over HTTPS. Keep tokens machine-specific so they can be rotated or revoked when hardware changes.
control
Project scope
Each repo is initialized with its own project root. Recall is project-scoped, and cross-project facts are filtered before the agent receives context.
control
Local daemon
Local mode can keep the daemon bound to 127.0.0.1 with a SQLite store on the developer machine. Use it when one laptop should hold both storage and recall.
control
Hosted app
Cloud moves setup, review, token management, and recall traces into the hosted app while agents continue to use explicit capture and recall requests.
control
Provenance
Memories can carry source events, lifecycle state, confidence, and recall traces. The goal is reviewed current truth, not untraceable transcript replay.
control
No training use
Your memories, sessions, and code are product data for your workspace. They are not used to train models.
control
Rotation and revocation
Retire a machine by rotating or revoking its token from the hosted path, then pair the replacement machine before it captures or recalls project memory.
control
Self-hosting
Enterprise is for teams that need the Cloud workflow deployed in their own environment with custom network, retention, and procurement requirements.