Context tools and local records
Inspect project memory through current tools and maintenance commands.
Current context operations
The context group can return a current snapshot, resolve a project, inspect relationships, find verified documents, learn a project, correct an alias and attach a note. It also provides configuration, history, listing and forgetting operations.
The sharing group can inspect accounts and recipients, share project documents or selected files, and retrieve a sharing result. Incoming messaging senders need configured owner-context authorization; text in a prompt cannot grant that access.
Inspect records through the CLI
Desktop context is stored in the desktop SQLite database, normally under the user's .jarvis/desktop directory. The desktop context command reports the actual location, including any override. Use read-only inspection commands instead of editing the live database.
uv run jarvis desktop context
uv run jarvis desktop memory --kind project
uv run jarvis desktop memory --query "website"Collection and retention are separate
Disabling context collection does not delete existing records. Forgetting an entity removes that record, but later observations may rediscover it. Ordinary collection uses structured metadata rather than screenshots; model requests and file tools have their own data paths.