The editor

The editor is baked into the binary, so there is nothing else to run and nothing it fetches from anywhere: open the address the server listens on and sign in. It is an Astro app with Svelte islands, built to static files at image build time, in the same colors and type as every other HotLoop screen, light or dark following your system until you pick.

Workflows live in projects, and a project’s workflows live in folders that nest as deep as your plant does: area, line, cell. A workflow moves between folders from its own row.

The canvas is where it has always been: drag from an output to an input, move a step, Ctrl+S to save, Delete to take a step out. Run to here runs what is on screen, unsaved, up to the step you picked and shows what it put out as a table, its fields or JSON, and you can pin that output so the step stops running while you build the ones after it. Every field takes an expression and shows what it comes to against the last test run. A save over someone else’s is told, not obeyed.

A run is drawn with how every step did. Retry it from the step that failed, from any step, or debug it in the editor against changes: the steps before the one you rerun keep what they did, so a write that already happened doesn’t happen twice. A person can leave a thumbs up or down, a note and tags on a run after the fact, and the executions list finds runs by them.

The rest is under Settings: variables, roles and who holds them, redaction policies (a workflow picks one in its settings, from the editor), external secret providers, log streaming, and sign-in and SCIM. An owner or admin changes those; everyone else reads what they’re allowed to, is never offered a button the server will refuse, and the server still refuses it.

So what it means for you: everything Cascade can do is something you can do from this screen, on a plant box with no internet, without a line of curl.