Jarvis.
Get source
JARVIS / DOCUMENTATION

Run locally

Start the assistant, inspect its services and return to your saved local work.

Start the voice runtime

From the configured project directory, run jarvis run. The plain jarvis command starts the same voice-first runtime. Keep the microphone and output devices available and wait for the actual connected/listening status.

Start with a small request, such as a focus timer.
Start with a small request, such as a focus timer. Illustrated example
PowerShell / source reference
uv run jarvis run

Inspect what is connected

Maintenance commands do not start a voice conversation. Use them to inspect desktop capabilities, job activity, current context and persistent project records.

PowerShell / source reference
uv run jarvis desktop status
uv run jarvis desktop activity
uv run jarvis desktop context
uv run jarvis desktop memory --kind project

Understand what persists

Ctrl-C stops the combined voice components. The separate desktop service can continue scheduled local work. Timers, reminders and context persist independently of the voice conversation; Windows and the service still need to be running for on-time delivery.

A new voice launch starts a fresh conversation rather than automatically resuming the prior dialogue. Persistent project notes and stored task history are separate retrieval capabilities.

Explore the practical workflows