Repair thread · 27 Aug 2026

Jarvis onboarding & voice: ask inventory

Scope is this Cursor thread only (not product analytics). Thirteen discrete asks from 26–27 Aug 2026. Code was shipped for most of them. User acceptance is still missing on the original seven bugs and on hold-to-talk.

Is this done?

No. The app currently opens. The screenshot of util.isError / usocket is the old 0.0.45 crash (/tmp/.mount_JarvisxD7qXy). The live process is Jarvis-0.0.47 with the dbus/usocket guard packed. That does not close the original repair: hold-to-talk, companion shaders, and onboarding were never user-verified after the crash.

13 asks tracked 8 shipped in code 4 unverified 1 still open (shaders)

Counts

Bucket N Meaning
Total discrete asks 13 Seven original bugs + six follow-ups in this thread
Answered in chat 13 Every ask got a response. None were ignored.
Shipped in a local AppImage 8 Implementation landed; some later rebuilt as 0.0.47
User-verified 0 No original bug was signed off. Crash screenshot is stale.
Still open / incomplete 5 Shaders never finished; four originals never re-tested after the open-crash

Original seven (26 Aug 02:04)

# Ask Answered? Status Evidence
1 Onboarding Continue crashes to a black screen Yes — treated as a bug, not a question Shipped, unverified Prior agent hardened onboarding hydration. You never confirmed Continue after the later AppImage crash.
2 Presence standby UI in onboarding looks wrong Yes — tied to overlay/presence work Shipped, unverified Shared presence shader exists. No visual sign-off.
3 Icon is a “J”; Windows desktop icon still T3; generate a real one Yes Shipped, unverified Linux packaging uses Jarvis icons. Windows .ico path was changed in code. No Windows machine in this thread.
4 Onboarding appears every launch Yes Shipped, unverified Persistence/hydration claimed fixed. Not re-tested after 0.0.45 failed to open.
5 Bloated command dialog; want Control Center / audio settings Yes Shipped, unverified Control Center (/jarvis) replaced the bloated dialog in code. Audio settings not acceptance-tested here.
6 Voice overlay stuck, no shaders, looks like a blob Partially — work started, never closed Open WebGL overlay + presence fragment exist. Micro-todo fix-companion-fluid-shaders still pending. You never accepted the look.
7 Voice does not work after Companion merge (worked in ~0.35) Yes — diagnosed, then reworked Partial Control Center mic test worked earlier. Hotkey auto-released at ~1.2s. Portal hold was implemented, then the AppImage died on usocket. Live 0.0.47 includes the dbus guard. Hold ≥5s still not user-tested.

Follow-up asks (26–27 Aug)

# Ask Answered? Status Notes
8 Linux hold-to-talk is fundamentally wrong — how do production apps do it? Yes Answered Verdict: xdg-desktop-portal GlobalShortcuts Activated/Deactivated. Briefing: jarvis-linux-ptt.plan.abstergo.fyi
9 Implement that for Windows and Linux, then install so I can test Yes Shipped, unverified Linux: portal first, honest tap fallback. Windows: uiohook hold. Installed; first 0.0.45 build crashed on open.
10 Multiple Jarvis installs — keep only the one we just built Yes Done Duplicate desktops/icons/old AppImages removed that night. Machine now has Jarvis-0.0.47 as the Applications copy (later rebuild, not 0.0.45).
11 App does not open: TypeError: util.isError is not a function in usocket/dbus-next Yes Fixed in running 0.0.47 Disable usocket under Electron; D-Bus over node:net. Packed string present in the live asar. Stale screenshot still shows mount JarvisxD7qXy.
12 Is this done? Yes — this briefing No Open-crash is fixed. Original repair is not accepted.
13 Collect every question, what we answered vs did not, export and analyze Yes This page Nothing in the thread was left unanswered as a question. Gaps are verification and shaders, not missing replies.

What we did not actually close

These are not unanswered questions. They are asks that still need a real device pass:

  1. Hold Ctrl+Shift+J ≥5s without auto-release; one release stops capture. Accept the GNOME shortcut dialog if it appears.
  2. Companion/overlay looks like a fluid shader, not a blob (ask 6 — still open in code todos).
  3. Onboarding Continue does not black-screen; onboarding does not reappear every launch.
  4. Control Center audio settings work the way you expect.
  5. Windows icon is Jarvis, not T3 — not testable on this Fedora box.

Sources