<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Prompt-Caching on ROBOCO</title>
    <link>https://roboco.io/en/tags/prompt-caching/</link>
    <description>Recent content in Prompt-Caching on ROBOCO</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 26 Jul 2026 10:00:00 +0900</lastBuildDate>
    <atom:link href="https://roboco.io/en/tags/prompt-caching/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Surprisingly, the Ralph Loop Is 9x Cheaper - The Economics of Context Caching</title>
      <link>https://roboco.io/en/posts/vibe-coding-token-experiments/</link>
      <pubDate>Sun, 26 Jul 2026 10:00:00 +0900</pubDate>
      <guid>https://roboco.io/en/posts/vibe-coding-token-experiments/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;A single-session loop that just states a goal and runs until done finished the same task at one-ninth the cost of a plan-driven workflow. The secret isn&amp;rsquo;t the loop — it&amp;rsquo;s the cache.&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;figure&gt;&lt;img src=&#34;https://roboco.io/posts/images/Dohyun.png&#34;&gt;&lt;figcaption&gt;&#xA;      &lt;h4&gt;Dohyun Jung - Principal Consultant, ROBOCO&lt;/h4&gt;&#xA;    &lt;/figcaption&gt;&#xA;&lt;/figure&gt;&#xA;&#xA;&lt;hr&gt;&#xA;&lt;p&gt;The Ralph loop is a simple approach. You specify only the goal and the completion criteria, then let the agent iterate autonomously in a single session until it passes the completion check. No plan document, no task decomposition, no handoff notes between sessions. At first glance it looks unplanned and inefficient.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
