Skip to main content

​
What are scopes?

Every memory can be tagged as work or personal, with an optional project name. This lets you filter your dashboard and briefings by context so work items stay separate from personal ones.

​
Tagging memories

When saving a memory, include scope and project naturally in your prompt: 
3ngram: Remember for the engram project (work): we chose PostgreSQL for the database
The AI sets scope: "work" and project: "engram" automatically based on your phrasing.

​
Scope mappings

You can configure persistent mappings so that any memory tagged with a project automatically gets the right scope. This saves you from repeating scope information every time. 
3ngram: Configure scope for project 'engram' as work
Now whenever a memory is saved with project: "engram", it automatically gets scope: "work" — even if you forget to specify.

​
Parameters

The configure_scope tool accepts:
ParameterRequiredDescription
projectYesProject name (case-insensitive)
scopeYeswork or personal
aliasesNoAlternative names that resolve to this project

​
Aliases

Aliases let you map multiple project names to one scope config. This is useful when the same project goes by different names across teams or tools. 
3ngram: Configure scope for 'consulting' as work with aliases 'dev' and 'engineering'
Now “dev”, “engineering”, and “consulting” all resolve to scope work.

​
Reapplying mappings

If you change a scope config and want to update existing memories to match: 
3ngram: Reapply scope mappings
This updates the scope on all memories whose project matches a mapping but currently has a different scope value.

​
Dashboard filtering

The dashboard supports filtering by scope. Switch between Work, Personal, or All to view just the items relevant to your current context.
Scope mappings require a paid subscription. Project names are case-insensitive and stored lowercase.