Back to guides

Update guide (CLI + App)

Update guide (CLI + App)

This guide explains the unified update flow built around a single command: `fusebase update`.

1) Command map

  • - single update command; behavior depends on current directory.
  • - same command, but skip app update stage explicitly.

2) Main scenarios

  • - outside an app project: updates CLI version only.
  • - inside an app project: updates CLI first, then updates the app.
  • - inside an app project with `--skip-app`: updates CLI only and skips app update.
Example result after `fusebase update`
Example update summary terminal output after fusebase update

3) Flags for `fusebase update`

  • - skip app update stage (CLI update still runs).
  • - skip agent assets refresh.
  • - skip MCP token and IDE config refresh.
  • - force MCP refresh even if markers are up to date.
  • - skip managed dependency sync.
  • - skip npm install after dependency sync.
  • - skip pre-update checkpoint commit.
  • - force checkpoint in non-interactive mode.
  • - print plan only, no writes.