Install locally
Start from Control Center so setup, repair, updates, rollback, and clean shutdown stay owned by the local runtime.
Developers
Build on Recall Core without breaking the local-first boundary.
Recall Core should feel like memory infrastructure: clear setup, explicit permissions, stable connection paths, and recovery behavior that does not leave users guessing.
Re:Yi official sitePublic content, local custody.Recall Core data stays outside the online service by default.
Quickstart shape
Local app first. API and MCP when the boundary is understood.
The public developer surface should help users install, connect, test, and recover. It should not require them to understand online service module internals before they can trust the product.
recall developer path
1. Install Control Center 2. Start the local runtime 3. Connect a trusted MCP client 4. Inspect permissions before syncing sources
Connect a client
Use local MCP first, then add API or SDK clients only when their access boundary is visible and reversible.
Choose memory sources
Bring notes, docs, chats, repositories, cases, and project records into a durable memory layer with explicit user intent.
Observe recovery
Retries, unavailable services, missing files, revoked packages, and permission problems should lead to a clear next action.
Contracts
Public, Admin, Control Center, and Core each own one job.
- Same-origin Re:Yi API for public pages
- Control Center owns local apply and rollback
- Admin owns public content and controlled release state
- Recall Core data stays outside the online service backend by default