JARVIS / DOCUMENTATION

Troubleshooting

Check the exact device, provider, integration or job before repeating an action.

Voice or task provider will not connect

Confirm that you are in the correct source directory and that its .env contains the intended Gemini and task-provider settings. Project-local voice values override inherited values. Inspect the error rather than assuming a different key or endpoint is being used.

PowerShell / source reference
uv run jarvis doctor
uv run jarvis model

Wrong microphone or speaker

List devices, identify the intended input/output and use the supported device options. Check operating-system device access and actual playback. A provider connection test does not prove that the physical microphone sounds correct.

PowerShell / source reference
uv run jarvis lowlevel --list-devices

Browser or editor context is missing

Load or reload the unpacked browser extension and confirm the connected profile. Reinstall/reload the VS Code adapter after updates when required. Check desktop status for the actual connection; an open window alone is not a connected adapter.

PowerShell / source reference
uv run jarvis desktop status

A task is partial or unconfirmed

Inspect activity with the returned job or command identity before repeating a modifying action. A sharing receipt is separate from recipient read status. A process exit alone is separate from a successful build.

When restarting after an update, desktop restart replaces the background service only when it has no active jobs. Restart the voice session afterward.

PowerShell / source reference
uv run jarvis desktop activity