Skip to content

Jarvis 0.2.0 — web UI, and a choice of front end

Choose a tag to compare

View all tags
@Explicabler1 Explicabler1 released this 02 Aug 16:48
· 42 commits to master since this release
v0.2.0
781c600

Jarvis now has two front ends, and the installer asks which one you want.

Install

Download Jarvis-0.2.0-Setup.exe and run it. Windows 10/11 x64, per-user by default (no admin). The setup wizard asks how you want to use Jarvis:
Desktop app native window, system tray, voice, artifact rendering
Web browser a local server you open in a tab

Both drive the same assistant — one composition root, the same skills, the same permission broker, the same memory. The choice is not permanent: it is the ui.mode setting, changeable in either front end's Settings screen, and both have a switch now button that starts the other one.

Upgrading from 0.1.0 keeps everything in %LOCALAPPDATA%\Jarvis — your key, memory, settings and generated skills.

The installer is unsigned, so SmartScreen will warn on first run — More info → Run anyway.

The web UI

Serves Core (chat with streaming replies and permission prompts), System, Skills and Files, plus the settings it is allowed to write.

It is not full parity with the desktop app, deliberately: no artifact rendering, no dashboard panels, and the file allow-list is read-only there — widening what Jarvis may read is a decision for the native app, not a browser tab.

Security, since this is a local server that can call tools:

  • Binds to 127.0.0.1, and mints a token per run that every /api route demands.
  • Loopback alone is not a boundary — any page you have open can POST to 127.0.0.1 — but it cannot read the page carrying the token, nor set the header cross-origin without a preflight the browser refuses.
  • Settings writes go through an allow-list, not a deny-filter.
  • Voice runs server-side: the mic button drives the microphone on the machine running Jarvis, not the one running the browser.

Command line

jarvis          whichever front end ui.mode names
jarvis gui      force the desktop app
jarvis web      force the browser UI
jarvis ui-mode  print the current mode; pass desktop|web to set it

The Start menu carries all three: a plain Jarvis shortcut that follows the setting, plus Jarvis (desktop app) and Jarvis (web UI) that force one — the escape hatch if the configured front end ever will not start.

Notes

~340 MB download, ~1.1 GB installed. Unsigned. x64 only. 655 tests pass.

Assets 3
Loading