How-to guides
Update, restart and uninstall
JARVIS Ultra runs as a service that starts on its own. These commands, run in the JARVIS Ultra folder (cd ~/jarvis-ultra), look after it. On Windows, run the uv commands in PowerShell and the .sh scripts in Git Bash.
See if it is running
uv run scripts/service.py status
It prints whether the service is installed and running, which process holds port 8830, whether the dashboard answers, and where the logs are. The last line is Status: running or Status: not running, and any problem: line says what to do.
To print the addresses you can open it at, the local one and the Tailscale one if published:
scripts/link.sh
Restart
uv run scripts/service.py restart
A restart never stops an agent in the middle of an answer on macOS and Linux. Missions that were planning or running when the server stopped come back as Failed with "Press Replan to start again."
Update
Run the install line again
Paste the same line you installed with, in Terminal (macOS, Linux) or PowerShell (Windows), for example:
curl -fsSL https://get.example.com/k7q2m9x4p8w3n6tz/install.sh | bash
iwr -useb https://get.example.com/k7q2m9x4p8w3n6tz/install.ps1 | iex
It sees that ~/jarvis-ultra (on Windows %USERPROFILE%\jarvis-ultra) is already an install and updates it in place:
==> Downloading JARVIS Ultra 1.32
==> Updating ~/jarvis-ultra to 1.32
Updating /home/you/jarvis-ultra from 1.31 to 1.32
Replaced 14 files, added 2, removed 1 (505 unchanged). The old copies are in .previous/.
Then the installer runs and restarts the service on the new version. If you installed with JARVIS_DIR, JARVIS_VOICE or JARVIS_NO_SERVICE, set them again the same way. When you already have the newest version, it says 1.32 is already installed in ~/jarvis-ultra. Nothing to do.
What an update changes and keeps:
- It replaces only the program's own files that changed, out of the ones the release lists in
release-files.txt. Your conversations, missions, board, settings and keys (data/), the logs, the team's documents (docs/), voices and installed packages are never touched. - Every file it replaces or drops goes to
.previous/in the JARVIS Ultra folder, which the next update empties first. - If the installer fails on the new version, the update puts the old files back, runs the installer on the old version again and prints why.
logs/update.logrecords each update.
Update from a downloaded archive
To update without the line, download the newest .tar.gz (or .zip on Windows) as in "Install from the archive" on your system's install page, then run, in the JARVIS Ultra folder:
uv run scripts/update.py ~/Downloads/jarvis-ultra-1.32.tar.gz
It does exactly what the line does. Add --voice or --no-service if you installed with them.
A git checkout
A copy you cloned with git is updated with git: git pull, then run ./install.sh (on Windows .\install.ps1) again. scripts/update.py refuses a git checkout.
The version you are on is the first entry of changelog.json in the JARVIS Ultra folder.
Uninstall
-
Stop and remove the service:
uv run scripts/service.py uninstallWith Piper voices installed, also run
uv run scripts/service.py uninstall --voice. -
If you published the dashboard on Tailscale, switch Publish JARVIS Ultra off first, or run
tailscale serve --https=8456 off. -
Delete the JARVIS Ultra folder. This deletes
data/too: your database, keys and backups. Download a backup first if you might come back.
Hermes and its agent profiles stay in ~/.hermes (on Windows %LOCALAPPDATA%\hermes), including the changes JARVIS Ultra made to them. Copies of the files as they were before JARVIS Ultra first changed them are in data/file-backups/ and data/config-originals/, so save those before you delete the folder if you want them. Remove Hermes with Hermes' own tools. uv and pnpm stay in your home folder.
Run it by hand
Without the service (for example after installing with --no-service), start the dashboard in a terminal and keep that terminal open:
cd api && uv run python -m app