A client's variables

Each client carries its own set of named values. A flow references them by token, so one flow can drive many clients, each using its own password, its own home coordinates, its own shop command.

Open Variables in the client's drawer. A row's fill in link takes you straight there.

Setting a value

You do not add variables by hand. The list fills itself: one row for every variable an attached flow reads, plus any value you already stored. A stored value that no attached flow reads any more is tagged not used.

Click Set value on an empty row, or Change on a filled one, type the value and save. Each row is tagged either secret or plain: secret when the flow writes it as {{secret:name}} or the name looks like a credential (a password, token or PIN), plain otherwise.

A plain variable is shown back to you. Use it for coordinates, warp names, a command prefix.

A secret is encrypted at rest. Once saved, the panel shows •••••••• (set) and the value is never shown again, never returned to the editor, and never printed in the client's log or console. Use it for passwords.

Click any token in the panel to copy it, ready to paste into a flow field.

What a flow sees

A flow written with {{home_warp}} reads that client's home_warp. Nothing about the value is stored in the flow, which is what makes a flow shareable, and what makes the Flow library safe: a published flow carries tokens, never values.

The password variable is the one the editor's Log in and Register blocks use.

Missing values

If an attached flow reads a variable this client has no value for, the client says so:

2 variable(s) still need a value. An attached flow reads these. The client will not start until you fill them in.

Starting, restarting or scheduling the client is refused until every required value is set, and the refusal names the ones that are missing. Variables are marked required or optional: an optional one is written {{name|fallback}} in the flow and falls back to that text while empty, so it never blocks a start.

Deleting

Deleting a variable is final. The stored value cannot be recovered, and any flow using it sends nothing in its place.

See variables and secrets for the flow-side view, including values a flow sets for itself while it runs.