update

/soloflow:update

Check whether a newer version of SoloFlow is available, surface any pending state migrations and (with explicit confirmation) apply them, and tell the user how to install a newer SoloFlow if one exists. This command never runs the soloflow code update itself — /plugin update (plugin install) or bash update.sh (script install) is user-driven. Migrations to project-local .soloflow/ state are the one mutation the command will perform, gated on an explicit AskUserQuestion confirmation.

---

Step 1: Refresh the version cache

Run via Bash:

node "${CLAUDE_PLUGIN_ROOT}/scripts/update/check-version.js" --force

Parse the JSON line on stdout. Fields you care about:

• current_version
• latest_version
• update_available
• channel — "dev" (this install is on the soloflow-dev channel) or "main" (the public soloflow channel). Drives the install command in Step 5.

If stdout is empty ({}) or missing fields, treat it as "could not check" and remember a single warning line:

Could not check for updates (network error or version unresolvable).
Try again later, or visit https://github.com/kesteva/soloflow for the
current version.

Print the warning and continue to Step 2 — migration status is independent of the version check.

Step 2: Check for pending state migrations

State migrations live under ${CLAUDE_PLUGIN_ROOT}/scripts/migrations/. They are project-local: each one reads/writes the current project's .soloflow/ and is idempotent. The run-all.js orchestrator walks every migrator in number order and reports what is pending.

1. Run via Bash, from the project root (the slash command's default cwd):

   node "${CLAUDE_PLUGIN_ROOT}/scripts/migrations/run-all.js"
   

2. Parse the JSON output. Field shape:

   • total_pending — integer count of migrators whose dry run produced changes.
   • migrators[] — per-migrator { id, pending, summary }.

3. If total_pending === 0: print No pending state migrations. and proceed to Step 3.