Workspaces & Files

What a workspace is, what Floah keeps in it, and the .flo flow file format.

A workspace is just a folder , opened via “Open Folder…” or “Clone from Git…” on the startup screen. Recently opened folders are offered as quick-open buttons the next time you launch Floah.

What lives in a workspace

• Flow files , any file ending in .flo, anywhere inside the folder. Each one is a complete graph: its nodes, their config, the wires between them, and the canvas viewport (pan/zoom). Opening one in the Explorer opens it as a flow tab; there’s no limit on how many a workspace can hold.
• code/<language>/ , one directory per enabled code language (code/go/, code/python/, code/typescript/), created the first time you enable that language in Settings. This is where the functions your Code Nodes call actually live. See Code Node.
• Environment variables , a workspace-scoped set of named values, one marked as the default, referenced from any field via ${env.NAME}. Manage them from the Explorer’s ⋯ menu → Environment Variables…. See Template Syntax Reference.

The Explorer

The left-hand file tree covers the whole workspace, not just flow files: new file/folder, rename, delete, drag-and-drop move, and a right-click context menu. Its ⋯ kebab menu also has Settings…, Environment Variables…, Open in Terminal, and Close Project.

Non-flow text files open in a lightweight in-app editor when clicked; .flo files open as a flow tab. The Explorer’s footer always shows whether VS Code is connected , see Code Node for the “Edit Src” workflow that uses it.