Skip to main content
Part 1 of the onboarding guide. Do this once per project.
1

Account setup

Goal: Everyone who will use FireWeave has an account, and the project is ready to receive repos.
  1. Go to https://app.fireweave.ai
  2. Register with your work email (this auto-joins you to your org)
  3. Complete your profile — name, role, GitHub handle
  4. Invite the rest of your team from Settings → Members
  5. Admin only: Connect PostHog and GitHub, create the project, and bind your logs, metrics, traces, and repository to the project dashboard
You land on the FireWeave dashboard and see your org, with PostHog and GitHub showing as connected and at least staging and production defined as environments.
If you see a create new workspace screen instead, your email didn’t auto-match. Contact FireWeave and we’ll fix the domain mapping.
2

Install the fw CLI

Goal: You have the fw binary on your machine, authenticated to your org. This is how the coding-agent plugin talks to our backend.Static, self-contained binaries are available for Linux x64/arm64, macOS x64/arm64, and Windows x64.
Verify the install:
fw login opens a browser. You authenticate, and the CLI picks up your tenant. fw whoami confirms your session.
fw whoami prints your email and your org’s tenant ID.
Your shell hasn’t picked up the new PATH. Open a new terminal, or run source ~/.zshrc / source ~/.bashrc. The installer puts the binary in ~/.fireweave/bin — add that directory to PATH if it isn’t already there.
Flag it with FireWeave and we’ll send a manual binary download link.
3

Install the FireWeave plugin

Goal: FireWeave shows up as a first-class plugin inside your coding agent, so your engineers don’t have to context-switch.
Three commands are available in your agent: /fireweave:initialise, /fireweave:safe-rollout, and /fireweave:cleanup.
4

Initialise the SDK

Goal: The SDK and the mapped capabilities are installed, and your runtimes can report what they’re running.Run this in your coding agent:
It runs mostly on its own and stops to ask you two things:Then:
  • Commit the fireweave/ folder (one per surface), the .fireweave/ folder, and the one line added to your entrypoint
  • Do not commit .fireweave/deploy-beacon.env.local
  • Copy FW_ATTEST_URL and FW_PROJECT_API_KEY from that file into your runtime
Without those two environment variables, rollouts never start.
The repo is initialised with no changes to your existing product code, and both runtimes hold the two environment variables.

​
Next

You’re ready to ship. Continue with Ship your first change.
Last modified on August 23, 2026