<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Fork on CodeInstances.com</title>
    <link>https://codeinstances.com/tags/fork/</link>
    <description>Recent content in Fork on CodeInstances.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 18 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://codeinstances.com/tags/fork/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CodeInstances Forks a Run at Any Step, to Run On Live or Try a What-If Answer</title>
      <link>https://codeinstances.com/codeinstances-forks-a-run-at-any-step-to-run-on-live-or-try-a-what-if-answer/</link>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://codeinstances.com/codeinstances-forks-a-run-at-any-step-to-run-on-live-or-try-a-what-if-answer/</guid>
      <description>&lt;p&gt;CodeInstances v0.6.0 adds fork. Replay runs a program against the whole recording. Fork runs it against the recording up to a step you pick, then lets it carry on from there. You get the past exactly as it happened, and a new future.&lt;/p&gt;&#xA;&lt;p&gt;Two uses pull this in. The first is picking up where a run went wrong. An agent ran for twenty minutes, called a dozen APIs, and on call nine it got an answer that sent it the wrong way. You don&amp;rsquo;t want to spend another twenty minutes and another dozen calls getting back to call nine. &lt;code&gt;codeinstances fork -at 9 run.instance&lt;/code&gt; answers calls one to eight from the recording in a moment, then sends call nine for real, against today&amp;rsquo;s servers.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
