Instrument as you build, deploy-sdk on npm & staging-to-prod promotion
Coding agents can now wire flags, metrics, and deploy attestation while they write the feature, @fireweaveai/deploy-sdk installs straight from npm, and rollouts promote from staging to production.
Instrument as you build
The rollout package no longer gets bolted on after the fact. With the new instrument-as-you-build substrate — deploy-sdk hooks, deploy attestation, and MCP tools for coding agents — your agent gates the code, registers its metrics, and mints deploy stamps while it writes the feature. By the time the PR opens, the rollout is already wired. See how it works.
@fireweaveai/deploy-sdk on npm
The SDK your services use to evaluate flags, emit metrics, and attest deploys is now published to npm as @fireweaveai/deploy-sdk, with stable and staging release channels. bun add @fireweaveai/deploy-sdk and you’re wired in.
Staging-to-prod promotion
Rollouts are now multi-environment: prove a change in staging, then promote the same rollout to production with its environment bindings carried over. A new setup UI walks you through binding each environment once.
Improved
- Deploy beacon CLI: one command provisions keys and environment for deploy attestation
- The initialise skill now wires the Cursor dev loop as well as Claude Code
Fixed
- Feature-flag provisioning recovers gracefully when the provider reports the flag already exists