Inspectable background jobs
Inspect accepted, running, completed, partial, failed and interrupted work through desktop activity and job results.
THE FIELD GUIDE / 09 — Background work & recovery
Go on with your day. Come back to a real result.
Watch a download or build, inspect long-running work, and undo supported actions.
Tell me when this download finishes.
JARVIS / IN EVERYDAY LIFEIllustrated possibilities. Your tools do the work.
01 / THE POSSIBILITIESA little more
A little more
within reach.
You should not have to keep checking a progress bar. Jarvis can follow actual browser downloads, connected editor tasks and desktop preparation jobs, then keep their outcomes in local activity records. When recovery is supported, those records also provide a way back.
See it in your dayDownload & task completion
Subscribe to real browser download events or the exit result of an identified running VS Code task.
Completion follow-ups
Attach a notification to a known job and report completion, failure or partial outcomes when the result arrives.
Guarded action recovery
Undo supported tab organization and file preparation outputs while checking for later changes. This is action recovery, not universal conversation rewind.
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
Leave the download to finish
You are waiting on a file but have something else you could be doing.
START WITH THIS
“Tell me when this download finishes.”
- 01
Start with the context
The connected browser identifies the actual download and registers a completion watch.
- 02
Let the work unfold
The adapter follows its real completion or interruption event instead of treating a file's appearance as a finished download.
- 03
Check the result
The desktop service records the outcome and uses the available notification path. Inspect the result if the download was interrupted.
THE RESULT TO LOOK FOR
A notification tied to a known download's reported outcome, subject to the browser connection and local service staying available.
THE EVERYDAY / WORKFLOW 02
Let a build finish without babysitting it
A connected editor task is still running and you want to switch to other work.
START WITH THIS
“Watch my running build in VS Code and tell me the result.”
- 01
Start with the context
Jarvis lists the actual running VS Code tasks and identifies the intended execution.
- 02
Let the work unfold
The adapter subscribes to that task's exit result and retains completion events across reconnects.
- 03
Check the result
The outcome is reported as success, failure or uncertainty based on available evidence. A generic process exit alone is not proof of a successful build.
THE RESULT TO LOOK FOR
The observed result of the specific editor task. A disconnected or unknown execution may require inspection rather than a success claim.
THE EVERYDAY / WORKFLOW 03
Undo the prepared copies, preserve the work
You want different export settings and no longer need the outputs from the previous batch.
START WITH THIS
“Undo that image preparation batch.”
- 01
Start with the context
Jarvis finds the supported action record and its batch recovery identity.
- 02
Let the work unfold
It checks all remaining outputs for later changes before performing the recovery.
- 03
Check the result
Unchanged generated outputs move into retained recovery storage. Modified files trigger a conflict instead of being silently overwritten.
THE RESULT TO LOOK FOR
Recovery for the supported recorded batch while retaining originals. It is not a blanket rollback of unrelated work.
Review local activity
Use the terminal activity view or ask the assistant to inspect jobs, watches and history.
uv run jarvis desktop activityConnect the actual event source
Browser downloads need the Chromium adapter; editor build results need the VS Code adapter. A generic file or process watch has narrower meaning.
Enable your preferred alerts
Native notifications need the companion and Windows settings. During voice conversations, completion announcements wait for an idle moment.
uv run jarvis desktop setup-notifications04 / A CLEAR PICTUREGood to know
Good to know
before you begin.
Accepted is not completed
An accepted job is queued work. A dispatched application command is not yet a verified result. Partial and unconfirmed outcomes deserve inspection before another attempt.
Recovery has a boundary
Only recorded, supported actions can be undone. Shell commands, external sends and arbitrary application changes do not become reversible just because Jarvis initiated them.
The natural next questions.
Workflow images are generated illustrations, not screenshots of a connected assistant. Availability depends on your configured tools and providers.
