Get started
Install on Windows
This is the native install for Windows 10 and 11 (Windows 11 is the reference). Nothing needs administrator rights. If you use WSL2, follow Install on Linux inside WSL instead.
Before you start
- Git for Windows with Git Bash, from
https://git-scm.com/download/win. MinGit is not enough: the team scripts and the agents' hooks run in Git Bash. If it is missing, the installer gets it withwinget, and Windows may ask you to approve that one install. - Your install line. Backers get it in a backers-only Kickstarter update; it looks like the example below, with a folder name of its own.
- About 15 minutes and an internet connection.
Install with one line
-
Open PowerShell (not as administrator) and paste your install line, for example:
iwr -useb https://get.example.com/k7q2m9x4p8w3n6tz/install.ps1 | iexIt downloads the newest release (
Downloading JARVIS Ultra 1.31), unpacks it into%USERPROFILE%\jarvis-ultra, unblocks its files and runs its installer there. It works even where running scripts is disabled, and it never closes your window: if something goes wrong, the last line starts withStopped:and says why. -
When Hermes asks for a provider (
No provider credential yet), open a new PowerShell window (the newhermescommand is only on the PATH of new windows) and sign in, for example:hermes auth add anthropic --type api-key hermes config set model.default claude-sonnet-5-5 hermes config set model.provider anthropicPaste your key (for example
<your-anthropic-key>) when asked.hermes modelruns the same steps as a wizard. -
Go back to the first window and run the installer again. It checks that Hermes answers and creates the team, which spends a few model turns:
powershell -ExecutionPolicy Bypass -File "$env:USERPROFILE\jarvis-ultra\install.ps1" -
Read the last lines. You should see
JARVIS Ultra answers at http://127.0.0.1:8830. Open it in your browser and set your password.A fresh install usually also lists one item underLeft to do:, telling the agents who you are, which the dashboard does on its first screen (First sign-in).
The line takes three settings, set in the same window before you paste it: $env:JARVIS_DIR = 'D:\jarvis' installs into that folder instead, $env:JARVIS_VOICE = '1' also installs Piper and eight voices, and $env:JARVIS_NO_SERVICE = '1' installs no Scheduled Task (see Options).
Install from the archive
The same folder holds each release as a file, if you would rather download it yourself:
-
Replace
install.ps1at the end of your line's address withlatestand open it in a browser, for examplehttps://get.example.com/k7q2m9x4p8w3n6tz/latest. It shows the newest version, such as1.31. -
Download
https://get.example.com/k7q2m9x4p8w3n6tz/jarvis-ultra-1.31.zip, right-click it, choose Extract All... and extract it into your user folder, so you getC:\Users\<you>\jarvis-ultra. -
In PowerShell:
cd $env:USERPROFILE\jarvis-ultra powershell -ExecutionPolicy Bypass -File .\install.ps1The installer unblocks its own folder first, so Windows' "downloaded from the internet" mark does not stop its scripts.
-
Go on from step 2 above.
What the installer does
| Step | What happens |
|---|---|
| Tools | Installs what is missing: uv in %USERPROFILE%\.local\bin, Git for Windows through winget. pnpm and Node.js (in %LOCALAPPDATA%\pnpm) only once you change the web app and it must be built |
| 1. The API's Python environment | uv sync makes api\.venv |
| 2. The web app | Comes built in web\dist. After you change the web app yourself, pnpm install and pnpm build build it here |
| 3. Folders | data\ (an access list lets only you read it), logs\ and docs\ |
| 4. Hermes | Installs Hermes into %LOCALAPPDATA%\hermes, with hermes.exe in %LOCALAPPDATA%\hermes\bin (added to your PATH) |
| 5. The team | scripts/create-team.sh sets up the Orchestrator and five specialists, once Hermes answers |
| Voice | Only with -Voice: Piper and eight voices (untested on Windows; the Browser voice works without it) |
| The always-on service | A Scheduled Task named com.jarvis-ultra.app that starts the dashboard at your logon, with no window |
The task runs while you are signed in to Windows and restarts the dashboard within a minute after a crash. Signing out stops it; signing in starts it again. If group policy blocks Task Scheduler, the installer puts a shortcut in your Startup folder instead, which starts the dashboard at logon but not after a crash.
Every step is safe to run again. Exit code 0 means nothing is left, 2 means the dashboard answers but a step is left for you, and 1 means a step failed (the Stopped: line says why).
Options
| Option | What it does |
|---|---|
-Voice |
Also installs Piper and eight voices |
-NoHermes |
Skips the Hermes and team steps |
-NoService |
Installs no Scheduled Task; start the dashboard yourself with cd api; uv run python -m app |
Running the team scripts
The team scripts are bash scripts. Run them in Git Bash, never in the bash.exe that comes with WSL. From PowerShell:
& "C:\Program Files\Git\bin\bash.exe" scripts/create-team.sh --verify
Or open Git Bash from the Start menu and run scripts/create-team.sh --verify in the JARVIS Ultra folder.
Check that it works
cd $env:USERPROFILE\jarvis-ultra
uv run scripts/service.py status
The last line reads Status: running. To check the port:
netstat -ano -p tcp | findstr :8830
It should show 127.0.0.1:8830 ... LISTENING and nothing wider. Task Scheduler (taskschd.msc) lists the task; its files are in %LOCALAPPDATA%\jarvis-ultra\services.
Now go on to First sign-in. If something stopped, see Install and service problems.