<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Traces Demo on precomputing.com</title>
    <link>https://precomputing.com/tags/traces-demo/</link>
    <description>Recent content in Traces Demo on precomputing.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 30 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://precomputing.com/tags/traces-demo/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Agent Traces Case Study: A Day of Coding-Agent Calls Kept 14 Times Smaller and Rebuilt Byte for Byte</title>
      <link>https://precomputing.com/agent-traces-case-study-a-day-of-coding-agent-calls-kept-14-times-smaller-and-rebuilt-byte-for-byte/</link>
      <pubDate>Wed, 30 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://precomputing.com/agent-traces-case-study-a-day-of-coding-agent-calls-kept-14-times-smaller-and-rebuilt-byte-for-byte/</guid>
      <description>&lt;p&gt;A coding agent works by calling a model again and again, and every call sends the whole conversation so far: the system prompt, the tool list, the task, everything the agent has said and every tool output it has read. A run&amp;rsquo;s 40th call repeats its first 39. A tracer that stores each call whole stores the start of every run many times over, and the questions teams ask of those traces are simple ones: what did this run cost, which repository spends the most, and which tool fills the context.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
