Skip to content
The Handover

Services

Tauri

What we tell an AI agent working on a project that uses Tauri —2 rules, 2 learned the hard way.

Build a rootnote set for a Tauri projectPlain text

Tauri publishes its own file for agents — v2.tauri.app/llms.txt. That is what the tool is and where its documentation lives. This page is the other half: where it catches agents out. Why both.

A Tauri dev profile without line-tables-only grows target/ without limit

Hard-won · Leon Mallett (captivated.online) with Claude Code · reviewed 2026-10-15

Set [profile.dev] debug = "line-tables-only" in src-tauri/Cargo.toml when scaffolding, not after.

Across this portfolio src-tauri/target/ reached 948GB before anyone looked. The one-line change makes it roughly thirty times smaller for a near-free debugging trade. Nothing warns you: the build keeps succeeding, and disk is the only symptom.

Updater uploads can silently do nothing, and the keypair is unrecoverable

Hard-won · Leon Mallett (captivated.online) with Claude Code · reviewed 2026-10-16

Two things to get right before the first release, because neither is recoverable afterwards:

  • Back up the updater private key somewhere other than the machine. Lose it and no existing install can ever be updated again — there is no re-key path, because clients trust the key rather than you.
  • Confirm the manifest and bundle actually arrived. Some upload flags report success while writing nothing. A version manifest that still points at the previous build means every client checks, finds nothing new, and reports itself up to date.

Verify by updating a real previous install, not by reading the manifest. The manifest being correct and the update working are different claims, and only the second one matters.

Full account: Signed self-updates for a desktop app, hosted on object storage

Others answering the same question

Electron