AI Release Engineer, live ramp control & CLI 2.0
Choose how much of a release Fireweave runs for you, steer a live ramp — amend the schedule, pick a rollback target, end the soak — and install CLI and plugins 2.0, which keep rollout state on the server and let CI authenticate with an organization API key.
AI Release Engineer
A new AI Release Engineer tab on the project lets you opt into automation, all off by default: detect deploys from GitHub Actions or the Deploy SDK, auto-ramp on healthy guardrails, and allow editing future stages of a live schedule. Binding an integration never turns an automation on — you do. Settings freeze into each rollout at seal.
Take the wheel on a live ramp
The ramp tracker is now an operator console. Amend future stages (double-confirmed), pick a rollback target — any earlier step, or back to 0% — and see the stability soak at full exposure, with a control to mark the release stable instead of waiting it out. Manual releases skip the soak; the first step has no Roll back, because there is nowhere to go.
CLI & plugins 2.0
fw and the Fireweave plugin are 2.0. Rollout manifests and change stamps live on the server — git keeps a pointer, instructions, and hooks, not a committed changelog. CI authenticates with FW_ORG_API_KEY (no device-flow profile). And when a session goes wrong, fw feedback packages a redacted report and uploads only after you say yes.
Improved
- Migrate an existing project from external PostHog onto internally managed Fireweave Control points infrastructure — the console copies them over, the migrate-harness skill rewrites the app
- Initialise wires the standalone Fireweave SDKs (@fireweaveai/sdk, @fireweaveai/web-sdk) instead of in-repo providers
- Observability and CI/CD are optional — a project can ramp on Control points alone
- One API keys tab holds both families: browser keys (fw_public_, rate-limited) and project deploy keys
- Internally managed Fireweave Control points infrastructure is the platform — it no longer appears as an external PostHog connector you install from the marketplace
- Access refusals render as a locked state, not a red error that begs a retry
Fixed
- A manual release moves only when a human moves it
- Rollback from the ramp/control route actually forwards the target you picked
- No Roll back on the first ramp step
- Evaluation stays pinned to internally managed Fireweave Control points infrastructure, not an external PostHog project
- Only organization owners and admins can manage project API keys