Tauri — AGENTS.md

# Tauri — AGENTS.md

## Architecture

Tauri apps have two layers:
- **Backend** (Rust): Native OS interactions, file system, IPC commands.
- **Frontend** (Web): UI rendered in system WebView. Communicates via `invoke()`.

## Project Structure

```
src-tauri/
  src/
    main.rs      # Entry point
    lib.rs       # App setup and command registration
  tauri.conf.json
  Cargo.toml
src/             # Frontend source
```

## Tauri Commands (IPC)

```rust
// Define a command
#[tauri::command]
fn greet(name: &str) -> String {
    format!("Hello, {}!", name)
}

// Register in main
fn main() {
    tauri::Builder::default()
        .invoke_handler(tauri::generate_handler![greet])
        .run(tauri::generate_context!())
        .expect("error while running tauri application");
}
```

```typescript
// Call from frontend
import { invoke } from '@tauri-apps/api/tauri';
const response = await invoke('greet', { name: 'World' });
```

## Development

```bash
# Prerequisites: Rust + Node.js
cargo install tauri-cli

npm install
npm run tauri dev    # Development mode
npm run tauri build  # Production build
```

## Security Guidelines

- **CSP**: Configure Content Security Policy in `tauri.conf.json`.
- **Allowlist**: Only enable required APIs in `capabilities`.
- **IPC Validation**: Always validate and sanitize data in commands.
- **Never expose** Rust backend paths directly to frontend.
- Use `tauri::path` module for safe path handling.

## Plugins

- Use official `tauri-plugin-*` packages for common functionality.
- Plugins follow `tauri::plugin::Builder` pattern.
- Each plugin gets its own capability scope.