/docs
Guide
Install Safety

Install Spark without guessing what happens.

Spark should feel inspectable. Download first, dry-run first, then install only after the plan makes sense.

Agent Markdown Checksums Manifest Signatures

The safety flow.

The safest way to install Spark is to preview the installer before it changes anything. Ask Codex, Claude Code, or another coding assistant on your computer to open this page, run the dry-run, and explain the plan in normal language.

01 Download

Save the installer as a file first. This lets you or your coding assistant inspect it before anything runs.

02 Verify

Compare the downloaded file with the checksum and release manifest published by Spark.

03 Dry-run

Preview the install. The dry-run should show where Spark will install, what it will download, and what commands it would run.

04 Install

Continue only after the plan is understandable and matches what you asked for.

05 Check

Run Spark verification, then confirm your Telegram bot, memory, LLM provider, and Mission Control are working.

Dry-run first.

These commands are meant to be readable by both people and local coding assistants. The dry-run should show what Spark would download, where it would install, which versions it would use, and which commands it would run.

Step 1

Preview a new install on macOS, Linux, or WSL

Use this when you are installing Spark for the first time on a Unix-style terminal.

curl -fsSL https://agent.sparkswarm.ai/install.sh -o spark-install.sh bash spark-install.sh --dry-run

After the preview looks safe, run bash spark-install.sh.

Step 2

Preview a new install on Windows

Use this when you are installing Spark from PowerShell.

iwr https://agent.sparkswarm.ai/install.ps1 -OutFile spark-install.ps1 powershell -NoProfile -ExecutionPolicy Bypass -File .\spark-install.ps1 -DryRun

After the preview looks safe, run the same command without -DryRun.

Step 3

Preview an upgrade when Spark is already installed

Use this when the docs mention a command your local Spark does not know yet, or when you want the latest installer improvements.

macOS, Linux, or WSL

bash spark-install.sh --dry-run --upgrade-existing

Windows

powershell -NoProfile -ExecutionPolicy Bypass -File .\spark-install.ps1 -DryRun -UpgradeExisting

Use upgrade mode when you already have Spark and want to preview what would change before updating.

What the installer is allowed to do.

A safe installer should be boring and predictable. Spark should only talk to expected places, write inside the Spark folder, and make startup changes only when setup says it will.

Allowed area 1

Downloads

  • agent.sparkswarm.ai for the installer and metadata.
  • github.com/vibeforge1111/spark-cli for the pinned Spark CLI release.
  • nodejs.org and github.com/astral-sh/uv when managed runtimes are needed.
Allowed area 2

Local files

  • Spark installs into ~/.spark on macOS, Linux, and WSL.
  • On Windows, Spark installs into %USERPROFILE%\.spark.
  • Logs, module sources, configs, and local state stay under that Spark home.
Allowed area 3

Startup

  • Autostart can turn Spark Live on when the computer logs in.
  • The dry-run should say whether startup files would be created or changed.
  • You can turn it off later with spark autostart uninstall.

What Spark can do after install.

Install safety is only the first layer. After your Telegram bot is connected, Spark asks what it should be allowed to do. Most people should choose 3.

1Talk only

Spark can answer in chat, but it will not build or inspect outside chat.

2Build only when asked

Spark can start build work only when you explicitly ask for it.

3Research and build when asked

Spark can inspect public links, docs, and repos when you ask, and can use Mission Control for builds.

4Broader local tools

For advanced local use. Spark can use broader operating-system tools, with guardrails and user approval for sensitive actions.

You can change this later from Telegram with /access 1, /access 2, /access 3, or /access 4.