dd37cdc5b4
Backup automation now emits `npx runfusion.ai backup --create` so scheduled backups work for users on the zero-install path where `fn` is not on PATH. `runfusion.ai` also exposes `fn` and `fusion` bins, so `npm i -g runfusion.ai` puts them on PATH (npm does not link dep bins globally). Alias only defaults to the dashboard when invoked as `runfusion.ai` / `runfusion`; `fn` / `fusion` forward args verbatim so bare `fn` still prints help. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
runfusion.ai
Launch Fusion with a single npx:
npx runfusion.ai
That command boots the Fusion dashboard and AI engine on port 4040. Prints an Open: URL with a bearer token you can click to open in your browser.
Subcommands
With no arguments, runfusion.ai defaults to dashboard. Any other subcommand is forwarded to the underlying fn CLI:
npx runfusion.ai # → fn dashboard
npx runfusion.ai task create "fix X" # → fn task create "fix X"
npx runfusion.ai --help # → fn --help
How it relates to @runfusion/fusion
This package is a ~1 KB alias. It declares @runfusion/fusion as a dependency and its bin delegates to the same entrypoint. Use whichever name reads better:
npx runfusion.ai
npx @runfusion/fusion dashboard
For persistent installs, prefer Homebrew or npm install -g @runfusion/fusion.
Links
- Website: runfusion.ai
- Source: github.com/Runfusion/Fusion
- Main package: @runfusion/fusion
License
MIT