A setup PR from Fireweave, Confirm what we found & Jobs
Fireweave reads your repositories, you confirm what it found, and it opens a setup PR per Managed repo — no local coding agent required. Finish setup and Jobs follow the run until you merge. The Fireweave SDKs are 3.0.0 on npm, PyPI, and crates.io, with a one-line start profile and Control points on the wire.
A setup PR from Fireweave
Choose Safe rollouts and Fireweave analyses the repos in its own sandbox — read-only. It opens one setup PR per Managed repository into the branch you pick. GitHub will ask existing installations to approve write access first; change release analysis keeps running while you decide. Merge the PR (or run /fireweave:initialise locally) and the repo is initialised — Control points and rollouts can start. Repositories that already have Fireweave setup stay initialised. Agent rules and hooks are a /fireweave:adopt to-do on the PR, not a commit Fireweave makes for you.
Confirm what we found
After analysis you land on Confirm what we found — apps, what they do, and which provider should serve Metrics, Logs and Traces. Change anything that looks wrong. Repositories are Managed (checks, setup, rollouts) or Context only (read for knowledge). Finish setup tracks each PR; if a run stops, it names why and takes your answers.
Jobs
A Jobs tab on the project lists setup, change release analysis and rollout runs — status, who started them, and a log when something fails.
Improved
- @fireweaveai/server-sdk and @fireweaveai/web-sdk are 3.0.0 on npm — import /start, set FIREWEAVE_KEY, and define Control points in one call; the web SDK adds /vite and /define for build-time browser keys
- fireweave 3.0.0 on PyPI and the fireweave crate on crates.io ship the same start profile; Go imports github.com/FireWeave-HQ/fireweave-sdk/sdks/go/v3 (sdks/go/v3.0.0 tag)
- SDK 3.0.0 names the public surface Control points — client.controlPoints, POST /v1/control-points/evaluate, and matching metadata keys — while fw-server keeps 2.x aliases; staging builds are 3.0.0-rc.N (Python 3.0.0rcN) and a -staging.N version no longer selects staging
- Each environment binds Metrics, Logs and Traces as their own connections — Logs and Traces are optional; Metrics is required only while auto-ramp is on
- Sentry can supply error-rate and latency as Metrics
- The marketing site footer links to Careers
Fixed
- Change release analysis no longer fails when the analysis sandbox takes longer than half a minute to start
- After a failed Control point refresh, prefetched SDKs keep serving the last good decisions with reason STALE instead of silently falling back to defaults