First-time setup

The onboarding flow turns a fresh install into a personalized Jarvis workspace. It appears only once unless you clear the local profile runtime file.

Startup flow

1. Splash screen loads and plays the startup audio.
2. Jarvis checks the local profile.
3. If onboarding is incomplete, the setup wizard opens.
4. After setup, Jarvis saves profile, permissions, memory location, workspace paths, theme, voice settings, and provider preference.
5. Future launches go directly from splash to the main UI.

User profile

The profile stores the preferred display name, usage type, personality style, theme, and provider preference. Usage type customizes suggestions and workflows for developers, students, creators, researchers, cybersecurity users, and general users.

Voice setup

Users choose whether Jarvis should listen for "Hey Jarvis" in the background or use manual activation only. Background listening is also controlled by Security & Permissions.

Workspace setup

Allowed workspaces define the folders where Jarvis can create, edit, organize, and generate projects. This is the safest place for autonomous code and file work.

Protected areas

Protected folders, files, and apps are always blocked by the permission engine. Good examples include password managers, banking files, personal photos, private documents, and security tools.

Memory setup

The wizard asks where Jarvis should store its local brain. The memory folder contains conversations, workflows, projects, preferences, voice data, browser history, automation logs, embeddings, cache, and backups.

AI provider setup

Users can choose a provider during onboarding, then refine models and keys later in Settings -> AI Providers. Keys entered in the app are stored by the backend and are not sent back to the frontend.