Current desktop context
Capture supported foreground-window, Explorer selection, browser and editor metadata. A snapshot anchors what you meant by ‘this’.
THE FIELD GUIDE / 02 — Context & project memory
A little less explaining. A lot more picking up.
Recognize the project, remember its other name, and keep the next step close.
Remember that this project is also called WA bridge.
JARVIS / IN EVERYDAY LIFEIllustrated possibilities. Your tools do the work.
01 / THE POSSIBILITIESA little more
A little more
within reach.
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.
See it in your dayProjects, aliases & checkouts
Find learned projects by name, preserve explicit aliases and distinguish a repository from its separate local checkouts.
Project notes & preferences
Keep a project checkpoint or an explicit preference in the appropriate local memory system, then inspect, correct or remove it.
History retrieval
Search stored task-agent conversations and recent desktop observations. A fresh voice launch does not automatically resume your old conversation.
Memory inspection & controls
Inspect entities, notes and their sources. Disable context collection separately from forgetting stored records.
02 / PUT IT INTO YOUR DAYOrdinary requests.
Ordinary requests.
Useful little transformations.
Follow the thought from the first sentence to the result. Make the names, files, and timing your own.
THE EVERYDAY / WORKFLOW 01
Use the name you actually remember
The folder has a formal repository name, but you always refer to it by a shorter name.
START WITH THIS
“Remember that this project is also called WA bridge.”
- 01
Start with the context
Jarvis resolves the active project from supported desktop context, or asks you to choose if several checkouts match.
- 02
Let the work unfold
Your explicit correction is stored as an alias of that project, with a stable identity.
- 03
Check the result
A later request such as ‘find WA bridge’ can resolve that stored alias before using approximate matches.
THE RESULT TO LOOK FOR
A project you can retrieve by the confirmed alias. Similar spelling produces choices rather than permission to guess.
THE EVERYDAY / WORKFLOW 02
Leave a useful checkpoint for tomorrow
You are about to switch projects and want the next session to start with a useful reminder of the work.
START WITH THIS
“For this project, remember that the next task is to update the screenshots.”
- 01
Start with the context
The current or explicitly named project is resolved; a named project takes precedence over the foreground window.
- 02
Let the work unfold
The supplied checkpoint becomes a note attached to that project's record.
- 03
Check the result
Later, ask to inspect the project notes. Jarvis can bring the checkpoint into a new task without claiming that the work has already happened.
THE RESULT TO LOOK FOR
A retrievable project note. It is not automatically a scheduled reminder, a calendar event or completed work.
THE EVERYDAY / WORKFLOW 03
Keep ‘these files’ tied to the right window
You have selected a few files in Explorer and want to refer to them naturally.
START WITH THIS
“What files are selected here?”
- 01
Start with the context
The voice path captures a context snapshot when speech begins, where supported.
- 02
Let the work unfold
Explorer selection is resolved from an identifiable active view. Multiple indistinguishable tabs are reported as ambiguous.
- 03
Check the result
A later file operation rechecks the referenced files rather than silently using whichever window you switch to next.
THE RESULT TO LOOK FOR
Observed paths for the intended selection, or a clear request for a more specific source. Context snapshots expire and may need refreshing.
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 project04 / A CLEAR PICTUREGood to know
Good to know
before you begin.
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.
The natural next questions.
Workflow images are generated illustrations, not screenshots of a connected assistant. Availability depends on your configured tools and providers.
Browser & workspaces
Organize your real tabs, carry useful information across apps, and return to a saved setup.
Files & media preparation
Find the file, read the screenshot, prepare a batch, and reuse the recipe.
Reminders & routines
Timers, notes, tasks and reminders that can take the relevant page along.