AuraOne / Docs / Agent Studio Open / Deep dive
Architecture
Tauri shell, Rust core, and Python sidecar. Local trace store and protocol adapters.
At a glance
Agent Studio Open guide
- Entry
- Architecture
- Reading
- 13 min
- Sections
- 1
- Applies to
- Applies to the current Agent Studio Open source release. Check the product page and repository for the latest version, supported platforms, and installation details.
01
System shape
A React/Vite interface inside a Tauri desktop boundary. A Python CLI and sidecar behind it. Trace storage, protocol adapters, and export generators are all local.
Capabilities differ by surface: browser mode blocks stdio, the OTLP receiver, and OS-keychain access; desktop and CLI paths expose local capabilities documented by the source repository.
- Renderer: the command palette, the connection panel, and the manifest inspector. Compose, observe, and ship live there too.
- Desktop boundary: native IPC and OS-keychain-backed operations where the Tauri runtime exposes them.
- Python sidecar: mcp-risk-linter, a2a-contract-test, tool-call-replay, agent-trace-card, otel-eval-bridge.
- Exports: a GitHub Action, JUnit XML, and PR comment Markdown. Also a trace card and an intake export.