Saving and sharing
Where flows are stored, how naming decides the filename, and the four ways to lose work you haven't saved.
Saving#
Type a name in the box to the left of the Run button, then press Save. The button reads Saving…, then flashes Saved ✓.
There's no dialog, no name prompt, no confirmation.
The flow is written to ~/.semantix/flows/, one file per flow:
~/.semantix/flows/my-review-flow.json
The filename is built from the flow's name — lower-cased, with every run of characters that aren't
letters or digits turned into a dash. "My Review Flow" becomes my-review-flow.json. A name that
reduces to more than 64 characters is refused, and the strip above the canvas says so.
Important
Two consequences of that, both worth knowing before they bite:
Saving overwrites silently. Two flows both left at the default name both become
untitled-flow.json, and the second one replaces the first without a word.
Renaming makes a copy. Change the name and press Save and you get a second file; the original stays exactly where it was, still in your Flows list. There is no rename.
Name a flow before you save it the first time.
Flows are stored per machine, not per project — one folder for all of them, whichever project you had open.
⚑ Four ways to lose work#
There is no autosave, no draft recovery, and no undo.
| Opening a flow | Replaces the canvas immediately. No warning, no "you have unsaved changes". |
| Reloading or leaving | An unsaved canvas is gone. Nothing is kept between sessions. |
| Deleting a node | Backspace, and it's not recoverable. Deleting a container takes its contents too. |
| Saving over a name | Silent, as above. |
The only recovery for any of them is reloading the last save.
The Flows panel#
Click Flows in the header. The panel opens on the far left, listing every saved flow, most
recently changed first, with a relative timestamp — just now, 12m ago, 3h ago, then a date.
Click a row to open it. The canvas is replaced, the name box adopts the flow's name, and the view fits to the new nodes.
A flow whose file can't be understood still appears, marked with an amber draft tag — hover it
for the reason. Broken flows are kept and listed rather than hidden; they just can't run.
To delete: hover a row, click the trash icon, then click again when it turns red and reads
sure?. Clicking elsewhere cancels. Deletion removes the file — there's no recycling bin and no
backup. If you had that flow open, the canvas is left alone.
Sharing a flow#
A flow file is safe to hand to another person. No credentials are ever written into it — it records only which model you picked, never the key or the URL behind it. Those are read from your own Semantix settings at the moment a flow runs.
What is in the file: your node layout, your wiring, your system prompts, the tools each agent carries, and a reference to each agent's model.
Important
The receiving side has to re-pick the models. A model reference is an id generated on the machine where that model was added, so it won't match anything in someone else's settings. They'll see "model … is not in custom-models.json" on the first run — opening each agent and choosing one of their own models fixes it. Everything else in the flow arrives intact.
To give someone a flow, send them the .json from ~/.semantix/flows/. To receive one, drop the file
into that folder — the Flows panel reads whatever is there.
Note
There's no import button in the app, so the folder is the door in both directions. The Export JSON button beside Save writes out whatever is currently on the canvas, saved or not, which is handy when you want the file without committing it to your Flows list.
Old flows keep working#
Flows saved under earlier versions of the composer load without a migration step. Retired node types still open — they render as plain nodes rather than failing — and tools recorded before the current naming still resolve. Where something genuinely can't run any more, the flow still loads; it refuses at run time, by name, so you can see what to replace.
Running a flow on a schedule#
Saved flows aren't only for the composer. Because they live in one known folder with a stable id, the Task Manager can run one on a schedule or on an event — the same flow you drew, firing while you're away.
Important
Deleting a flow that a task refers to breaks that task the next time it fires. The task doesn't notice until then.