JARVIS UltraManualv1.31

Reference

Files and folders

Everything JARVIS Ultra keeps, and where. <root> is the JARVIS Ultra folder; <hermes> is Hermes' home (~/.hermes, or %LOCALAPPDATA%\hermes on Windows).

<root>/data/: your runtime state

Owner-only (mode 700 on macOS and Linux, an access list on Windows). Not in git. Back it up with Settings > Backups, never by sharing the folder.

Path What it holds
jarvis.db The database: agents, conversations and messages, missions, approvals and decisions, the Board, schedules and runs, rules, notifications, usage (turns), MCP servers, your skills' records
sessions.db Browser sign-ins
auth.json Your password, as a salted hash
owner.yaml Your brief
providers.json Which providers you added (no keys)
provider-<name>.key One provider key per file
composio.key, elevenlabs.key The Composio and ElevenLabs keys
mcp/<id>.token Tokens for MCP servers that use one
vapid.json The key that signs push alerts
agent-options.json Each agent's fallback, timeout, retries, tool lists and skill switches
voice.json Voice settings
integrations.json Your app connections
tailnet.json The last Tailscale address and port
chat-files/ Files attached in Chat
backups/ Backups, as b-<date and time>-<code>.tar.gz
docs-deleted/ Documents you deleted from Docs
docs-aside/ Documents a restore moved aside
file-backups/ A copy of every Hermes file before the dashboard changed it (never cleaned up)
config-originals/ Each agent's config.yaml as it was before the tools lock was first added
skills/ Your skill store: published files, drafts, and changed copies kept aside (kept/)

<root>/docs/: documents

Path What it holds
docs/<profile>/ An agent's documents, for example docs/researcher/
docs/orchestrator/ The Orchestrator's documents and every mission result
docs/you/ Documents you write in Work > Docs
docs/install.md, docs/remote-access.md Part of the program. remote-access.md is the guide behind Settings > Remote access > Setup guide.

Document files are named <YYYY-MM-DD>_<title>.md.

<root>/logs/

Path What it holds
jarvis.log The server's log, rotated at 5 MB, three kept
service.log Start-up output of the service
turns/ What Hermes printed for each agent turn (never cleaned up)
voice.log The Piper voice service's log
tailscaled.log JARVIS Ultra's own Tailscale node, when it runs one
mcp-signin/ Output of MCP sign-ins
update.log What each update did: the versions, how many files it replaced and removed, the installer's result

Other folders in <root>

Path What it holds
api/, web/, scripts/, deploy/ The program; web/dist comes built (web/dist/PREBUILT holds its version)
voice/ The Piper voice service; voice/.venv, voice/models and voice/cache after the voice install
.tailscale/ JARVIS Ultra's own Tailscale node, when it runs one
.jarvis-env Optional: KEY=VALUE lines the service starts with (Ports and environment variables)
changelog.json The version history; its first entry is the version you run
release-files.txt Every file of the release you run; an update replaces only these
.previous/ The files the last update replaced or removed, kept until the next update
LICENSE, THIRD_PARTY_LICENSES.txt What you may do with JARVIS Ultra, and the licenses of the web app's packages
manual/ This manual

<hermes>: the agents

Path What it holds
SOUL.md, memories/, config.yaml, .env, auth.json, skills/ The Orchestrator's profile
profiles/<name>/ Every other agent's profile, with the same files
profiles-archived/<name>/ Retired agents
agent-hooks/ Scripts the dashboard gives agents: asking for approval, hiring, the app launcher and the tools lock, plus the dashboard's address and key
logs/install.log Hermes' install log

In each profile, the dashboard also writes jarvis-tools.grants (which apps the agent may use, and how) and, while an approved change is being carried out, jarvis-tools.allow. MCP sign-ins are in mcp-tokens/.

The service

System Files
macOS ~/Library/LaunchAgents/com.jarvis-ultra.app.plist (com.jarvis-ultra.voice.plist for voice)
Linux ~/.config/systemd/user/jarvis-ultra.service (jarvis-voice.service for voice)
Windows Scheduled Task com.jarvis-ultra.app; its files in %LOCALAPPDATA%\jarvis-ultra\services