Settings reference
Every edition reads and writes one shared settings file, and each edition surfaces the same fields through its own interface. The fields are described once in a manifest, tagged per-edition, and rendered the same way everywhere.
One shared settings file
Section titled “One shared settings file”Settings live in a single ~/.flow-studio/settings.json, the same data
directory shared across editions. Because the file is shared, a change made in
one edition is read by the others when they next load it.
Per-edition field manifest
Section titled “Per-edition field manifest”The available fields come from a field manifest. Each field is tagged with the editions it applies to (Desktop, Server, Code, and CLI), and every edition renders the manifest the same way. An edition shows the fields tagged for it, so the layout and meaning stay consistent no matter where you open settings.
Flow Code
Section titled “Flow Code”In VS Code, Flow Code adds a Settings editor tab that renders the manifest fields for the Code edition, grouped into the same sections and order as the desktop app, alongside provider-key management for the opt-in cloud providers. The Settings control is reachable from the sidebar header described in Interface and controls.
Flow CLI
Section titled “Flow CLI”Flow CLI exposes the same settings through a settings command, and the
TUI has a settings screen that renders the manifest fields for
the CLI edition.