Skip to main content
fw is the Fireweave command-line tool. You use it to authenticate, bind a git repo to a Fireweave project, install coding-agent plugins, pull server-owned repo state, and run local checks. It is a static binary. Latest production release: 2.5.2 (tag fw-cli/v2.5.2-production, 2026-09-08).
Rollouts and feature flags are not CLI commands. There is no fw rollout and no fw flag. You register and inspect rollouts in the Fireweave console and through coding-agent skills / MCP tools. The one CLI exception is fw pr check — a pre-merge readiness gate, not rollout control — and it is not generally available.

​
What you use it for

Typical first session:
In CI, after the repo is bound, you authenticate with an org API key and run fw sync. See Authentication.

​
Install

The installer downloads a platform binary from S3, verifies its checksum, installs it to ~/.fireweave/bin, and wires that directory into your shell so new terminals — and shells a coding agent spawns — can find fw.
Supported targets: Linux x64 and arm64, macOS x64 and arm64, Windows x64.
The installer downloads from the us-east-2 bucket by default. Set FW_INSTALL_BASE to override the base URL if you were given a different tree.
The installer writes one managed file, ~/.fireweave/env, and sources it from a marked block in ~/.bashrc, ~/.profile, ~/.zshenv, or fish conf.d. On Windows it updates the user Path. Re-running the installer does not add a second block. fw self-update replaces the binary only. It does not re-run the installer. If fw is missing from PATH after an upgrade, run fw doctor --fix.

​
Version and channel

fw --version prints the embedded version and the distribution channel that produced the binary:
A staging-channel build prints (staging). Channel matters: it changes where fw self-update pulls from, and it changes the default cloud fw login targets.

​
Upgrade

fw fetches latest/manifest.json from the channel tree, compares (version, channel) against the running binary, downloads the matching artifact, verifies SHA-256, and atomically swaps ~/.fireweave/bin/fw. A version-only comparison is not enough. Both channels publish the same clean semver, so switching channel is a reason to install even when the version string is unchanged. There is no background auto-update. You run fw self-update yourself.

​
Staging

Install or switch to the staging channel when you were asked to dogfood a pre-production CLI:
A staging binary defaults fw login to the staging cloud. Pass --cloud to log into production from a staging build, or --staging to log into staging from a stable build. See Authentication.

​
Scope

fw is a thin client over Fireweave’s management plane. It stores login profiles under ~/.fireweave/ and a per-repo binding under .fireweave/. After fw init, use /fireweave:safe-rollout in your coding agent to register a rollout. Use the Fireweave console to inspect or abort one.

​
Next

Authentication

Interactive fw login and CI FW_ORG_API_KEY.

Command reference

Flags and exit codes for every visible command.
Last modified on September 11, 2026