tauri-plugin-auditaur
Development-first Tauri v2 plugin for collecting Auditaur local telemetry.
Use this crate in a Tauri app to create a local Auditaur session database, receive frontend telemetry from @auditaur/api, record Rust tracing spans/logs, capture Tauri window lifecycle state, and expose the data to auditaur-cli and MCP tools.
Install
[]
= "0.1"
= "0.1"
= "0.3"
Register the plugin
use ;
IPC trace bridge
Backend commands can opt into frontend-to-backend trace continuation:
The frontend wrapper sends W3C traceparent through the Tauri invoke request headers and keeps the older reserved auditaurTraceContext invoke argument as a compatibility fallback. The auditaur_command macro wraps #[tauri::command], injects both IPC carriers, prefers the request header, falls back to the reserved argument, and adds the tracing::instrument fields Auditaur needs.
If you need to keep an explicit #[tauri::command], use the lower-level #[tauri_plugin_auditaur::instrument_ipc] macro with an optional auditaur_trace_context: Option<IpcTraceContext> argument.
A healthy invoke trace has a frontend tauri.invoke load_user span, a tauri_ipc_calls row with the same trace/span ids, and a backend child span with the same trace id and parent_span_id set to the frontend span id. App integration tests can assert that shape with:
assert_trace_stitched;
Safety note
Auditaur is development-first. Release builds are blocked unless allow_release_builds(true) is explicitly configured.