Inventory the Tauri desktop surface for the GPUI migration

Draft
CO
2mo ago
+352-0

Summary

Problem: ANLG-320 Phase 0 requires an inventory of every Tauri command, plugin, window, frontend route, background service, and OS integration, each mapped to shared core, GPUI replacement, or approved removal, before any UI porting. Nothing like that exists, so the size of Phase 1 (shell-neutral backend) and the list of WebView-only surfaces are both guesswork.

Fix: Add apps/desktop-gpui/docs/tauri-inventory.md, generated from main at 38d2fc67d and hand-classified. It covers 48 first-party plugins (364 commands), 19 app-level commands, 16 third-party Tauri plugins, 8 windows, 9 routes, 40 frontend feature areas (with TypeScript LOC and the Rust services each depends on), 14 background services, and 22 OS integrations. Each row is mapped to one of four outcomes: core (already runtime-neutral in crates/*), extract (logic trapped in the plugin crate; Phase 1 work), gpui (needs a native implementation), or remove? (WebView-only; candidate pending an explicit decision).

Findings that shape the next phases:

  • 22 of 48 plugins carry logic that must be extracted before both shells can share it. plugins/db alone is 14.2k Rust LOC of CloudSync lifecycle, E2EE identity, legacy import, and startup status; transcription + local-stt are 6.5k; attachment-sync 3.8k. The document ends with a proposed Phase 1 extraction order.
  • The WebView live-query transport (db::execute/subscribe/...), webview_health_*, fake-window overlays, js::eval, relay, fs2, and six third-party plugins exist only to serve the WebView and are listed as removal candidates; none are removed here.
  • The settings schema lives in TypeScript (apps/desktop/src/settings/schema.ts); it has to become a Rust type both shells read, which is called out under Phase 1.
  • Packaging/signing/updater-compatibility surfaces owned by tauri.conf.*.json and tauri-build are enumerated so Phase 2's "packaging, signing, CI targets" checkbox has a concrete list.

The mapping column is a decision and will need review by people who own these areas; the counts and the command appendix are mechanical and can be regenerated.

Verification

  • Command counts and names come from plugins/*/permissions/autogenerated/commands/*.toml and apps/desktop/src-tauri/src/commands.rs; plugin LOC and backing crates from plugins/*/Cargo.toml and src/; frontend LOC from apps/desktop/src/*.
  • Summary table totals reconciled against the per-row classifications (48 = 13 + 22 + 8 + 5, etc.).
  • pnpm exec dprint check on the new file.
  • Documentation only; no build or runtime change.
Open in Web Open in Cursor