Scylla Memory carries durable project context forward so useful decisions and implementation history do not disappear when a chat ends or an Agent Provider changes.
Team Memory extends that idea across an organization.
It is context, not authority.
Knowledge and Memory are different
Scylla deliberately separates these concepts.
Knowledge
User-selected non-project folders that contain reference material such as plans, architecture notes, research, handoffs, and other context.
Memory
Durable project context Scylla can retrieve from local and, for Team, hosted Memory sources.
A useful shorthand is:
Knowledge = material you choose
Memory = context the work carries forward
Neither one grants execution authority.
Project source is different again
Workspace Scope contains project/code folders.
Knowledge Scope contains non-project reference folders.
Memory contains durable contextual records and indexed information.
Do not treat Memory as a hidden source-code checkout or as a permission system.
What Team Memory is for
Team Memory can help preserve context such as:
- implementation handoffs;
- active plans;
- architecture blueprints;
- durable project decisions;
- known constraints;
- recent project context;
- shared retrieval across team members when the organization/project binding allows it.
The exact categories visible depend on the current Memory implementation and data available for the project.
Project binding matters
Memory must resolve against the correct Scylla project.
A Memory result for cxl-scylla should not silently become the Memory result for cxl-scylla-workbench merely because the names share a prefix.
Scylla treats project identity as an exact runtime concern.
If Memory appears empty or unavailable, first verify the active project and Team account/organization context.
Local and Team Memory
Scylla can work with local Memory and hosted Team Memory as distinct sources.
The desktop may merge or present results from those sources through the Memory browser, but service state and content state are not the same thing.
For example:
Connected + zero entries
means something very different from:
Service unavailable
Scylla should not claim "No Memory entries" merely because a service request failed.
Memory is not authority
Memory may tell an Agent:
Production deploys use this sequence.
That does not grant permission to deploy.
Execution still goes through the applicable:
- Workspace Scope;
- Access/connection requirements;
- Policy;
- Broker;
- provider/capability boundaries.
Memory can inform an operation. It cannot authorize it.
Team Memory and outages
A Team Memory outage should degrade context availability.
It should not widen Agent authority or make unrelated local development impossible.
Local project work should continue where the rest of Scylla is available.
Privacy and secrets
Do not use Memory as a credential store.
Protected values belong in Keyring/connection paths designed for secrets.
Credentials, private keys, raw .env values, and reusable tokens should not be intentionally written into Memory.
If you need an Agent to work with a protected service, prefer a saved Connection or brokered operation rather than storing the secret as project context.
Enabling Team Memory
The exact controls depend on your Team role and current Workbench deployment.
A normal Team flow is:
- Sign in to the correct Scylla Account.
- Confirm Team membership and entitlement.
- Open the Team Memory settings in the authenticated Workbench console.
- Enable/configure the organization Memory service if your role allows it.
- Return to desktop and let Scylla refresh Team service state.
- Open a project that has an appropriate Memory binding/context.
If provisioning is asynchronous, treat Provisioning as a real intermediate state rather than assuming the service is ready immediately.
Using Memory in the desktop
Use the Memory browser/search to inspect what Scylla actually has for the current project.
Useful checks include:
- active project identity;
- source of the Memory result;
- whether hosted Team service is connected;
- whether local Memory is available;
- whether results are present;
- whether a project binding is missing.
Common states
Connected
The Memory source is reachable.
Empty
The source is connected, but no matching entries were returned.
Provisioning
Hosted Memory is being prepared.
Not configured
The project/account does not yet have the required configuration or binding.
Unavailable / degraded
The service could not satisfy the request. Do not interpret this as empty content.
Common problems
Team Memory is visible on the website but not desktop
Confirm the desktop is signed into the same Scylla Account/organization and refresh account state.
Memory says unavailable
Check service status and project binding. Do not delete local Memory merely because a hosted request failed.
Wrong project's context appears
Stop and report it. Project identity must be exact.
Agent knows something from Memory but cannot perform the operation
That is expected when Policy or another authority layer blocks it.