Agent Start Here

Use Auditaur data before asking a developer to paste logs, screenshots, browser console output, or terminal output.

Install the agent skill

In a repo that uses Auditaur, scaffold the shared debugging skill so agents know the readiness, CDP, telemetry, screenshot/snapshot, and cleanup workflow:

auditaur init skill

To scaffold into another repository path:

auditaur init skill --path D:\projects\my-tauri-app

After the skill is present on the Auditaur repository’s default branch or published by maintainers, agents/users with GitHub CLI skill support can install it directly:

gh skill install sethjuarez/auditaur auditaur-debug

From the Auditaur repository, maintainers can validate the publishable skill without creating a release:

gh skill publish .github --dry-run

gh skill preview reads from GitHub, so previewing sethjuarez/auditaur will only find auditaur-debug after the branch containing .github/skills/auditaur-debug/SKILL.md is pushed/merged.

Startup mode choice

Use attach mode as the default: start the app through the developer’s normal workflow, then have Auditaur observe it.

$env:WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS='--remote-debugging-port=9222'
npm run tauri dev
auditaur debug --app my-app --active --cdp-port 9222 --json watch --until-ready

Use wrapper mode when an agent or smoke script should own a repeatable validation run:

auditaur debug --app my-app --active --cdp-port 9222 --json run --timeout-seconds 180 -- npm run tauri dev

Wrapper mode starts the same app command you would have run manually; Auditaur does not replace Tauri startup. It watches readiness and leaves the app running after readiness so the agent can drive, inspect, or clean it up.

Integration docs

• Add Auditaur to a Tauri App
• Migrate from tauri-plugin-log
• Tauri Plugin
• Frontend API
• CLI Reference
• MCP Tools

First checks

auditaur doctor
auditaur apps --json

If exactly one active readable session exists, Auditaur commands discover it automatically. If multiple sessions are active, copy databasePath from auditaur apps --json and pass it with --db.

When debugging restarts, inspect auditaur apps --json before assuming Auditaur restarted the app. Stale entries can include supersededBySessionId, secondsUntilNextStart, and churnHint when a newer session for the same app appears, which often points to an app restart or Tauri dev watcher rebuild.

Fast failure triage

auditaur errors --json
auditaur exceptions --json
auditaur traces --failed --json
auditaur ipc --failed --json
auditaur events --json

Start with frontend errors, failed traces, failed IPC calls, and recent events. Prefer JSON when another tool or model will inspect the output.

For production-style exception triage, use auditaur exceptions --json to group repeated frontend exceptions, Rust panic-hook records, and failed IPC calls by fingerprint. Use auditaur exceptions --fingerprint <id> --markdown --output issue.md when you need a GitHub issue-ready draft, and redact it before sharing outside the machine.

Follow causality

When a failing trace or IPC call includes a traceId, inspect the full trace:

auditaur trace <traceId> --json
auditaur timeline --trace <traceId> --json
auditaur explain --trace <traceId>

Use the trace detail to connect frontend actions, Tauri invokes, Rust logs/spans, Tauri events, and frontend listeners.

Live debugging

auditaur tail

Use tail while the app is running to watch new logs, errors, spans, IPC calls, and events.

Shareable context

auditaur bundle --redacted --output auditaur-bundle.json

Use a redacted bundle when a bug report or handoff needs a bounded snapshot of the local session.

MCP equivalent

The MCP server exposes the same data for agents that support MCP:

auditaur mcp

Prefer the CLI for quick scripted checks and use MCP when the agent can call tools directly.