Local SQLite
Project context on the local machine.
Scylla Memory
Scylla Memory carries useful project context beyond a single conversation. Preserve decisions, plans, handoffs, and findings so the next task can start with the work already understood.
Scylla Memory uses SQLite for local storage and PostgreSQL for configured remote storage. Local Memory supports continuity on your machine; remote Memory supports shared context where configured. Remote Scylla Memory is encrypted at rest.
Project context on the local machine.
Configured remote context, encrypted at rest.
Active project files and source code
Reference material you deliberately make available
Durable context carried forward from the work
Memory informs the agent; Security Policy governs its actions. Keep reusable credentials in Keyring rather than storing them as project context.
Keep architecture decisions, active plans, implementation findings, and handoff information available to future work. Changing conversations or providers should not require rebuilding the project’s background.
Authorized members can use shared context after their desktop receives the organization’s relevant configuration. Availability depends on the organization, project binding, and enabled service.
Explore Teams →