Context and memory
Recognize the project, remember its other name, and keep the next step close.
How it fits into your day
A project is more than a folder name. It has a local checkout, a repository, a few important files and the nickname you actually use. Jarvis can connect observed desktop context to persistent project records, then keep explicit notes attached to the right thing.
Inspect current coverage
The desktop service collects supported structured context with the voice runtime. This command shows what it can actually observe.
uv run jarvis desktop contextConnect your working applications
Install the browser and VS Code adapters for richer context. Configure existing project root folders for bounded discovery; unknown projects are not preloaded.
Inspect stored project memory
Read the current records without modifying the local database.
uv run jarvis desktop memory --kind projectScope and availability
Context has a specific scope. Ordinary collection uses structured metadata without screenshots. Unsupported application internals remain unknown; file changes do not prove which document you read.
Local records, configured processing. Project records live locally. Context used in a model request can be sent to the provider you configured. Disabling collection does not erase existing records; forgotten entities can be rediscovered through later observation.
A practical first request
The folder has a formal repository name, but you always refer to it by a shorter name.
Try: “Remember that this project is also called WA bridge.”
A project you can retrieve by the confirmed alias. Similar spelling produces choices rather than permission to guess.