screenpipe-tauri
screenpipe-tauri manages Tauri command handlers and TypeScript bindings for the screenpipe desktop application. Use this skill when adding or modifying #[tauri::command] functions in Rust, updating exported types, or regenerating frontend bindings via the automated tauri-helper crate and bun scripts.
git clone --depth 1 https://github.com/screenpipe/screenpipe /tmp/screenpipe-tauri && cp -r /tmp/screenpipe-tauri/.claude/skills/screenpipe-tauri ~/.claude/skills/screenpipe-tauriSKILL.md
# Screenpipe Tauri (desktop app)
Path: `apps/screenpipe-app-tauri/`
Command registration is automated via the `tauri-helper` crate. **Do not** edit manual invoke-handler or specta command lists in `main.rs`.
## Adding a command
1. Add **both** markers to the handler function in any `src-tauri/src/**/*.rs` module:
```rust
#[tauri::command]
#[specta::specta] // required — without this the command is skipped in tauri.ts
pub async fn your_command(...) { ... }
```
2. From `apps/screenpipe-app-tauri/`:
```bash
bun run bindings:generate # write lib/utils/tauri.ts
bun run bindings:check # verify no drift
bun run typecheck # verify frontend types
```
3. Commit Rust + `lib/utils/tauri.ts` together
## Scripts
| Command | Purpose |
|---------|---------|
| `bun run bindings:check` | Fail if checked-in `lib/utils/tauri.ts` does not match Rust |
| `bun run bindings:generate` | Regenerate `lib/utils/tauri.ts` after command/type changes |
| `bun run typecheck` | Frontend TypeScript check |
## Key files
- `src-tauri/build.rs` — `tauri_helper::generate_command_file` (build-time scan)
- `src-tauri/src/main.rs` — `specta_collect_commands!()` / `tauri_collect_commands!()`
- `src-tauri/src/specta_bindings.rs` — export helpers and drift tests
- `lib/utils/tauri.ts` — generated TypeScript bindings (checked in)
Debug builds also auto-export bindings on startup when content changes.Release the screenpipe monorepo. Bumps versions, triggers GitHub Actions for app, CLI, MCP, and JS packages.
Query the user's data via the local screenpipe REST API at localhost:3030 — screen recordings, audio, UI elements, usage analytics, and the user's persistent memory store. Use when the user asks about their screen activity, meetings, apps, productivity, media export, retranscription, connected services, OR when they ask to save / remember / store / note information so it can be retrieved later (POST /memories — survives across sessions and is queryable by Claude/external agents via the same API).
Manage screenpipe pipes (scheduled AI automations) and connections (Telegram, Slack, Discord, etc.) via the CLI. Use when the user asks to create, list, enable, disable, run, or debug pipes, or manage service connections from the command line.
Check Screenpipe health status, process state, and diagnose common issues
Retrieve and analyze Screenpipe CLI backend logs and desktop app logs for debugging
Query the org's screenpipe telemetry as an enterprise admin — devices, members, recent activity, and substring search across the team's screen recordings and audio transcripts. Use when the user asks about their team, a teammate's activity, what their organization worked on, app usage across the org, or anything that requires seeing data beyond the user's own machine. The skill is only installed for enterprise admins; ordinary users won't see it.