How do I safely deploy code written by Claude Code?
Keep using Claude Code. Fireweave adds its instructions so the change arrives with a control point, the pull request gets a risk report, and you approve the rollout plan. The change then ramps from 1% to 5% to 25% to 100% while guardrails watch error rate, latency and business metrics, and a bad change is flipped off without a redeploy.
Steps
- Keep using Claude Code. Fireweave adds its instructions once, so the change arrives with a control point and the metrics that guard it.
- The pull request gets a risk report: the risk level, the blast radius (which services the change can reach), and the control points and metrics added.
- Fireweave suggests a rollout plan. You can approve it, edit any step, or turn off automatic rollback, and you start the rollout.
- The change ramps from 1% to 5%, then 25%, then 100%. Each step waits for its soak timer and for guardrails to pass. Guardrails watch error rate, latency and business metrics. The wrapping guide’s recommended default also includes a 50% step.
- If a guardrail trips, Fireweave flips off only that change. There is no redeploy, and the other changes in the release keep serving.
Read next
- Product: what the release engineer does.
- Getting started: connect a repo and start a rollout.
- Wrapping a feature: how the agent wraps the change.
- Fireweave vs LaunchDarkly: ramp and rollback next to a feature-flag platform.