-
Notifications
You must be signed in to change notification settings - Fork 0
api tauri commands
factory-droid[bot] edited this page Jul 5, 2026
·
1 revision
Active contributors: Douwe de Vries, vriesd
Tauri commands are the local API used by the renderer. They expose Session, Entry, Draft, Finding, attachment, settings, provider, and generation operations.
| File | Purpose |
|---|---|
src-tauri/src/commands/sessions.rs |
Session commands. |
src-tauri/src/commands/entries.rs |
Entry commands. |
src-tauri/src/commands/findings.rs |
Finding commands. |
src-tauri/src/commands/generation.rs |
Generation commands. |
src-tauri/src/commands/settings.rs |
Settings commands. |
src-tauri/src/commands/files.rs |
File and clipboard commands. |
src-tauri/src/commands/providers.rs |
Provider status commands. |
src-tauri/src/specta_bindings.rs |
Command registration and binding export. |
frontend/src/tauri.ts |
Frontend wrapper layer. |
src-tauri/src/commands/error.rs maps core errors into frontend-safe command errors. Frontend code formats these through helpers such as frontend/src/ui/format.ts.
Commands connect Frontend shell to Rust core. AI commands connect to Generation jobs.
- QA Scribe
- Download overview video (MP4)
- Architecture
- Getting started
- Glossary
- By the numbers
- Lore
- Fun facts
- Video overview
- How to contribute
- Development workflow
- Testing
- Debugging
- Patterns and conventions
- Tooling
- Applications
- Desktop app
- Smoke harness
- Systems
- Rust core
- Tauri command bridge
- Frontend shell
- Generation jobs
- Provider detection
- Release tooling
- Features
- Session capture
- Rich record editing
- Managed attachments
- AI-assisted Testware
- Settings and provider setup
- Crates
- qa-scribe-core
- qa-scribe-app
- Primitives
- Session
- Entry
- Finding
- Draft
- Evidence
- API
- Tauri commands
- Deployment
- Security
- Background
- Architecture decisions
- Migration context
- Cleanup opportunities
- TODOs and FIXMEs
- Complexity hotspots
- Reference
- Configuration
- Data models
- Dependencies