Automate Tauri command registration via tauri-helper.

[divanshu-go]

Description

Replaces hand-maintained Tauri invoke-handler and tauri-specta command lists with build-time auto-collection using tauri-helper at 65d4f27. Adds drift tests so checked-in TypeScript bindings stay in sync with Rust, and regenerates lib/utils/tauri.ts with stable alphabetical ordering.

Motivation

The screenpipe Tauri app had grown to ~200 commands spread across many modules. Every new #[tauri::command] required manual updates in three places:

1. tauri::generate_handler![...] in main.rs
2. tauri_specta::collect_commands![...] in main.rs
3. Often a follow-up regeneration of lib/utils/tauri.ts

Missing a step caused runtime handler errors or stale frontend types. This PR removes that maintenance burden and adds CI-friendly guards against binding drift.

Changes

Rust backend (apps/screenpipe-app-tauri/src-tauri)

Area	Change
Dependency	Adds tauri-helper as a git dependency (build + runtime) pinned to 65d4f27
build.rs	Calls tauri_helper::generate_command_file with collect_all: true to scan the workspace for all #[tauri::command] functions at compile time
main.rs	Removes ~200 lines of manual command lists; uses tauri_helper::specta_collect_commands!() and tauri_helper::tauri_collect_commands!() instead
main.rs	Introduces define_specta_builder! macro shared by debug export, tests, and the specta registry
specta_bindings.rs	New module with TypeScript export helpers and drift tests
package.json	Adds bindings:check and bindings:generate bun scripts (wrappers around the drift tests below)

Frontend (apps/screenpipe-app-tauri)

Area	Change
lib/utils/tauri.ts	Regenerated from the auto-collected command surface; commands and types are alphabetically ordered for stable diffs

How it works

At build time, tauri-helper walks the Cargo workspace, finds every function annotated with #[tauri::command], and writes generated macro input to target/tauri_commands_list/. At compile time:

• specta_collect_commands!() expands to the full tauri_specta::collect_commands![...] list
• tauri_collect_commands!() expands to tauri::generate_handler![...]

Adding a new command is now: write #[tauri::command], rebuild — no list editing.

Binding export & drift detection

From apps/screenpipe-app-tauri/:

# Fail if lib/utils/tauri.ts drifted from Rust (run in CI / before PR)
bun run bindings:check

# Regenerate lib/utils/tauri.ts after adding or changing #[tauri::command]
bun run bindings:generate

Equivalent cargo test invocations (what the bun scripts call under the hood):

cargo test -p screenpipe-app tauri_bindings_are_current --manifest-path src-tauri/Cargo.toml -- --nocapture
UPDATE_TAURI_BINDINGS=1 cargo test -p screenpipe-app export_typescript_bindings --manifest-path src-tauri/Cargo.toml -- --nocapture

In debug builds, main.rs also calls write_bindings_if_changed_with on startup so local dev stays in sync without manual export.

Test plan

• cargo check -p screenpipe-app succeeds with the pinned tauri-helper git dependency
• bun run bindings:check passes in apps/screenpipe-app-tauri (checked-in tauri.ts matches Rust)
• bun run typecheck passes in apps/screenpipe-app-tauri
• bun run build completes (Next.js + pre_build)
• App launches; spot-check invoke paths (settings load/save, recording start/stop, permissions)
• Add a new #[tauri::command] in a submodule and confirm it appears in the handler without editing main.rs

Notes

• No behavior change intended — this is a registration and tooling refactor. Command names and signatures are unchanged; only how they are collected and exported differs.

• Stable diffs — tauri.ts reordering is cosmetic (alphabetical).

[louis030195]

@divanshu-go can you remove unrelated change from the pr

generated by the screenpipe pr-review pipe (https://screenpi.pe), not written by a human — reply and tag @louis030195 if it got something wrong.

[divanshu-go]

@louis030195 removed the unrelated changes from this PR.

I also changed Specta’s bigint export from BigInt to Number in specta_bindings.rs:

Typescript::default().bigint(BigIntExportBehavior::Number)

Reason: Tauri IPC serializes through JSON, so the frontend receives JS number values at runtime, not bigint. This only affects the generated TypeScript bindings. Rust still uses u64 / i64, and serde behavior is unchanged.

The values we expose are safely below Number.MAX_SAFE_INTEGER, so number matches the real runtime behavior without precision issues.

Screen.Recording.2026-05-29.at.5.49.23.PM.mov

[divanshu-go]

@louis030195

Screen.Recording.2026-05-29.at.6.25.57.PM.mov

[divanshu-go]

@louis030195 I'm currently rebasing it , So I will ping you once its done.

[divanshu-go]

@louis030195
#3688