Flow Studio overview
Flow Studio is the desktop edition of Flow. It is the shipped foundation that the other editions build on. It is a Tauri 2 shell that hosts the React canvas UI over the shared Rust orchestration core.
What ships in Studio
Section titled “What ships in Studio”- A multi-tab canvas workspace. Each flow document is independent and has its own runs, undo history, and persistence. Canvas and workspace.
- Agentic and autonomous runs. You can generate flows from natural language, review them before they are applied, and monitor runs. The platform works toward a flow that runs cleanly, and it stays within the budgets you set. Agentic and autonomous runs.
- Scheduling. Saved flows run on cron or recurrence schedules, with timezone handling and catch-up policies. Scheduling.
- The Model Hub. You can browse, download, verify, and load local LLMs that
are served by a managed
llama-server. Model Hub. - The Template Hub. You can browse and download complete flow templates. Template Hub.
- The Node Hub. You can install catalog-driven node types into your library. Node Hub.
- Execution history. Every run is recorded in SQLite, whether it is manual, scheduled, agentic, or from the CLI. Each record keeps per-step detail and interception snapshots.
The process model
Section titled “The process model”The Tauri shell is a thin host. It registers command wrappers, manages a single application-core instance, and forwards events. All real logic lives in the shared Rust core, which integration tests exercise without any desktop dependency. The same core powers Flow Code, Flow Server, and Flow CLI unchanged.
Security posture
Section titled “Security posture”Local inference is zero-egress by default. There are two carve-outs, and both are opt-in and off by default. They are cloud AI providers and service-node APIs. Both are gated by settings, and their credentials live in the OS keyring. The shell adapter runs with always-on lightweight rails and an opt-in OS sandbox. See Zero egress and Sandboxing.
Data locations
Section titled “Data locations”| Location | Contents |
|---|---|
~/.flow-studio/db/flow.sqlite | Execution history |
~/.flow-studio/settings.json | Application settings |
~/.flow-studio/templates/ | Saved flows (.flow.json + .flow DSL projection) |
~/.flow-studio/llms/ | Downloaded local models |
~/.flow-studio/engines/ | The managed inference engine |
~/.flow-studio/nodes/ | Installed node schemes |
~/.flow-studio/logs/ | App tracing + the shell audit log |
| OS keyring | Cloud AI keys, connection secrets, never on disk |
You can override the data root with the FLOW_STUDIO_DIR environment variable.
The CLI and desktop share it, so runs from either surface land in one history.
Related editions
Section titled “Related editions”Flow Code is the VS Code edition, and it is built on the same core. See Flow Code.