Skip to main content

First-Run Checklist

Pre-flight​

  • Get the app for your device and follow Installation.
  • Enable microphone and headset/device permissions for the features you use.
  • Have your verified Telemus account and active license ready. See Licensing and account access for signup, verification and billing.
  • Have a supported AI provider key ready, use the available OpenAI/Codex OAuth flow, or choose demo mode and connect AI later.

In-app setup​

First run guides you through account setup, comfort and a first workspace task. The normal room and navigation controls stay locked until the Ready step is finished. Device Link and the optional channel setup remain available within the flow. Progress can be resumed if setup is interrupted.

  1. Welcome: choose a dot character: Ember, Azure, Lumen, Moxie, Sprig, Sunny, Sol, Echo or Pip. Ember is the default. Preview and availability indicators show what the current device can display. A preview is not confirmation that the character has activated on another device.
  2. Sign in to Telemus: open account login or create an account in the browser. Finish the verified device-link flow before continuing.
  3. Input & comfort: choose hold-to-talk or tap-to-talk, text size, reduced motion, seated mode and contrast where supported.
  4. Connect AI: select CONNECT PROVIDER. Keep the Device Link card open, scan its QR code or enter the displayed code in Telemus Portal, then save your provider settings. API KEY CONNECTED allows you to continue with that key; OPENAI / CODEX OAUTH is a separate text/model connection. Voice and other provider services may require API-key access. DEMO MODE is available when credentials are not ready.
  5. Connect a channel (optional): choose a connector in Quick Connect, then use Open Portal, Test and the displayed setup steps. Choose how Telemus should respond. Use Finish Later, More Channels or Skip as needed.
  6. First turn: ask “What can you help me with?” by voice or text.
  7. Create workspace: make your first persistent note or open the task board.
  8. Restore context: save a snapshot and check that your work can be restored.
  9. Ready: finish setup, then explore account settings and other supported integrations at your own pace.

If Finish asks you to reconnect your account, complete the displayed Device Link flow and tap Finish again. Use the same code in the browser and app. Expired codes are replaced with a new one. If the headset cannot open a browser, use the QR code or full URL on your phone or computer.

On Quest, open the menu if a required panel is outside your view. Reopening show_onboarding also brings it back in front of you. Ordinary status updates keep the panel in place.

After setup, use show_onboarding to reopen the guide, skip_onboarding where available, and show_help for topic-specific guidance. These controls do not bypass account or license requirements.

You can change the character later in Settings. The terminal /avatar command lists the same choices; /avatar <id> selects one. Older Telemus, Nova and Orbit choices map to Ember, Azure and Lumen. Character names do not select an AI provider. Custom GLB upload is not available in this picker.

Account linking does not require an AI model. At SIGN IN TO TELEMUS, choose Link Telemus AI Account before configuring a provider. If linking fails, check the displayed account or network error; adding a model is not the fix.

Once setup has completed, an offline period or expired device credential should not erase that completion. Use License Status and reconnect controls for account recovery. AI turns, tools and sync still require current access.

If an older build lost the completion record, complete the normal verified Finish flow again. If Device link request failed appears without a code card, update to the current available build and retry.

If secure storage cannot be read or updated, linking remains blocked. Collect the displayed error for support. Do not delete your workspace or manually edit credentials to work around it.

Account deletion​

Delete Account can delete your remote account. Do not use it to test local recovery. Follow the displayed confirmation and completion messages carefully. A completed local cleanup does not by itself confirm remote account deletion. If storage problems leave cleanup pending, contact support with the error rather than assuming deletion finished.

Research Workflow Option​

Where Start Research or Research Workflow is available, it opens a starter workspace with a task board and review card. Use it to collect evidence, review pending actions, export a read-only brief and resume work later. Availability depends on your build and release channel.

Continuity sanity check​

  • Restart once and confirm the saved workspace returns.
  • Check that the note or task you created remains present.
  • Reopen the task board, help and terminal where supported.
  • Inspect any pending confirmation before continuing a sensitive action.

If you can get one answer, create one workspace item and save the room, your first working session is complete. For help, see Configuration and Credentials and Troubleshooting.