<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Ashwik Reddy</title>
    <description>The latest articles on DEV Community by Ashwik Reddy (@ashwik_reddy_00b9b6eae9a3).</description>
    <link>https://dev.to/ashwik_reddy_00b9b6eae9a3</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1712651%2F0d69a6fb-ad2c-444c-9d2c-50149d60e68a.png</url>
      <title>DEV Community: Ashwik Reddy</title>
      <link>https://dev.to/ashwik_reddy_00b9b6eae9a3</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/ashwik_reddy_00b9b6eae9a3"/>
    <language>en</language>
    <item>
      <title>Agents write code in minutes. Releasing it safely still takes hours</title>
      <dc:creator>Ashwik Reddy</dc:creator>
      <pubDate>Fri, 13 Nov 2026 01:59:24 +0000</pubDate>
      <link>https://dev.to/ashwik_reddy_00b9b6eae9a3/agents-write-code-in-minutes-releasing-it-safely-still-takes-hours-5fjf</link>
      <guid>https://dev.to/ashwik_reddy_00b9b6eae9a3/agents-write-code-in-minutes-releasing-it-safely-still-takes-hours-5fjf</guid>
      <description>&lt;h2&gt;
  
  
  The problem
&lt;/h2&gt;

&lt;p&gt;Claude Code, Cursor and Codex can turn a ticket into a PR in minutes. But merging is where the speed stops.&lt;/p&gt;

&lt;p&gt;After merge, someone still has to:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;decide how risky the change is&lt;/li&gt;
&lt;li&gt;roll it out without exposing every user at once&lt;/li&gt;
&lt;li&gt;watch error rates, latency and business metrics&lt;/li&gt;
&lt;li&gt;roll it back fast if something goes wrong&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That work is still manual, spread across CI, flag tools and dashboards. As agents open more PRs, release has become the bottleneck, and the risk grows with every change.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why it's getting worse
&lt;/h2&gt;

&lt;p&gt;Most teams treat &lt;strong&gt;deploy&lt;/strong&gt; (code reaches prod) and &lt;strong&gt;release&lt;/strong&gt; (users see the change) as one event. That was manageable when people wrote every line. With agents, more changes ship faster, and each one gets less human attention.&lt;/p&gt;

&lt;p&gt;We think deploys and releases have to be decoupled. And not only for "features": a refactor, a dependency bump or a config change can break prod just as easily.&lt;/p&gt;

&lt;h2&gt;
  
  
  Our solution: Fireweave
&lt;/h2&gt;

&lt;p&gt;Fireweave is a release management platform that works alongside your coding agent:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Code:&lt;/strong&gt; your agent writes release-ready code. Fireweave plugs into Claude Code, Cursor, Codex and Cline.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Prepare:&lt;/strong&gt; each PR gets a risk score.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Release:&lt;/strong&gt; the change is wrapped in a &lt;em&gt;control point&lt;/em&gt; and ramps from 1% to 100%.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Verify:&lt;/strong&gt; guardrails check error rate, latency and business metrics in real time.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Recover:&lt;/strong&gt; if a guardrail trips, that one change rolls back automatically.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;strong&gt;Control points&lt;/strong&gt; are versioned flags. Every deploy creates a new version of every control point, even the ones that didn't change, so there's always a known-good version to roll back to.&lt;/p&gt;

&lt;p&gt;Fireweave works with your existing CI/CD and observability; it doesn't replace them.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Coming soon:&lt;/strong&gt; coordinated rollouts across services, cohorts, agent skill versioning, and feature locks so two agents or devs don't work on the same feature at once.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;See it in 2 minutes, no signup:&lt;/strong&gt; &lt;a href="https://fireweave.ai/product" rel="noopener noreferrer"&gt;https://fireweave.ai/product&lt;/a&gt;&lt;br&gt;
Pick a sample PR and watch a healthy rollout, an automatic rollback, or take manual control of the ramp yourself.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Use it on your own repo:&lt;/strong&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Sign up free: &lt;a href="https://app.fireweave.ai/signup" rel="noopener noreferrer"&gt;https://app.fireweave.ai/signup&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Connect GitHub.&lt;/li&gt;
&lt;li&gt;Open a PR, read the risk report, and turn on a safe rollout.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Docs: &lt;a href="https://fireweave.ai/docs" rel="noopener noreferrer"&gt;https://fireweave.ai/docs&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  We'd love to hear from you
&lt;/h2&gt;

&lt;p&gt;Once you've tried it, drop a comment:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;What was your first impression?&lt;/li&gt;
&lt;li&gt;Does decoupling deploys from releases fit how your team ships?&lt;/li&gt;
&lt;li&gt;What would make you keep using it?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;We read and reply to every comment.&lt;/p&gt;

</description>
      <category>showdev</category>
      <category>infrastructure</category>
      <category>ai</category>
      <category>devops</category>
    </item>
  </channel>
</rss>
