Scylla

Scylla Memory

Keep the context. Continue the work.

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.

Local and remote storage.

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.

Local SQLite

Project context on the local machine.

Remote PostgreSQL

Configured remote context, encrypted at rest.

Three kinds of working material.

Workspace

Active project files and source code

Knowledge

Reference material you deliberately make available

Memory

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.

Useful context across the project.

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.

Shared Memory for teams.

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 →