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, your usage is tracked on your account, 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. Add a Cloud file sink node to your graph and it saves incoming frames to 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 tracking: compute and storage

Your account now tracks what you use:

  • Compute — runtime seconds spent in saved 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 this is record-keeping only — nothing is capped or blocked based on usage. You can inspect your numbers at /admin/usage-ledger. Usage-based limits will arrive in a later release.

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.

Notes

  • If you hit unexpected behaviour when starting a run, please file an issue and include the correlation ID from the error message.
  • The 0.2.0 CLI is backwards-compatible with your existing login and paired devices.

Coming next

  • Usage visibility on your own account pages.
  • Plan-aware usage limits (free, paid).
  • Capture and replay files between the CLI and the cloud.