0.2.0 — Release Notes

0.2.0 turns SerialFlow from a per-session tool into a persistent workspace. Projects you build, runs you complete, and frames you capture are all saved to your account, account-aware usage is metered against a ledger, and the CLI gently nudges you when it’s out of date.

Highlights

Persistent workspace

Projects and the sessions inside them are now saved to your account.

  • Project library. A dedicated library lists every project on your account; reopen one and Studio reattaches to its active runtime if a run is still going. Auto-save kicks in when you start a run, so you can’t lose a graph between edits and execution.
  • Reviewable runs. Stopped and failed runs keep their terminal output. Re-opening a finished run shows the historical transcript instead of an empty terminal — useful for debugging after the fact, sharing context with a teammate, or comparing two runs side by side.
  • Saved Data + cloud capture. A new “Saved Data” library lists frame recordings captured from your runs. Recordings are produced by the new cloud_file_sink graph node, which streams incoming frames into durable cloud storage in the background while your run is live. From the library you can inspect recordings and play them back through any compatible source.

Usage metering: compute and storage

Each account now accrues usage against a ledger covering:

  • Compute — runtime seconds spent in durable sessions (rolling-window and 7-day totals).
  • Storage operations — durable writes attributable to projects, runs, and sessions.
  • Storage size — bytes retained on your behalf.

Today the ledger is observability-only — it records what you use, and does not enforce caps. A read-only admin surface at /admin/usage-ledger lets account holders inspect the data. Enforcement (admission denials and runtime termination on quota exhaustion) ships behind feature flags and is rolled out progressively.

CLI version check

The SerialFlow CLI now lets you know when a newer release is available. On invocation, the CLI checks GitHub for the latest published release and prints a one-line nudge to stderr if the version you’re running is outdated. The check is non-fatal — network errors, missing releases, and non-interactive shells (CI, scripts) are silently tolerated.

To opt out entirely, set SERIALFLOW_NO_VERSION_CHECK=1.

Studio polish

  • Leave-warning. Navigating away from Studio while a device is connected or a run is active prompts before discarding the in-flight state.
  • Context preserved across navigation. Internal navigation (settings, library, etc.) returns you to Studio with your graph and runtime intact instead of a fresh load.

Heads up

  • The persistent-workspace admission path is enabled by default; ledger-based enforcement is not. If you hit unexpected behaviour around session creation, please file an issue with your correlation ID.
  • The 0.2.0 CLI is backwards-compatible with the existing token and device flows.
  • cloud_file_sink requires an object-store backend to be configured on the deployment.

Coming next

  • Per-account usage visibility outside the admin surface.
  • Tier-aware enforcement (free, paid) once we’ve validated ledger numbers in production.
  • File-streaming over the CLI bridge (capture and replay across the local <-> cloud boundary).