<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Tool Output on Programmer.ie: Modern AI programming</title>
    <link>http://programmer.ie/tags/tool-output/</link>
    <description>Recent content in Tool Output on Programmer.ie: Modern AI programming</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 23 Sep 2026 05:00:17 +0100</lastBuildDate>
    <atom:link href="http://programmer.ie/tags/tool-output/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Remove What No Longer Matters</title>
      <link>http://programmer.ie/books/context/10-chapter/</link>
      <pubDate>Wed, 23 Sep 2026 05:00:10 +0100</pubDate>
      <guid>http://programmer.ie/books/context/10-chapter/</guid>
      <description>&lt;p&gt;Nine chapters have observed, classified, measured, ordered, priced, and architected around context without once deleting anything. That restraint ends here, and it should end nervously. A team ships an automatic cleanup pass over its coding agent&amp;rsquo;s history: exact-duplicate tool outputs go, failed calls older than four turns go, anything the model flags as done goes. Token counts fall by a third. Two weeks later a migration guardrail the team believed was load-bearing starts failing silently. The deleted material contained the only record of a constraint the project file never stated, a decision reached mid-session and never written anywhere else. Nobody summarised it away. Nobody rewrote it. It was simply removed, by a rule that could not tell a redundant copy from a unique original.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Tools Produce Context</title>
      <link>http://programmer.ie/books/context/17-chapter/</link>
      <pubDate>Wed, 23 Sep 2026 05:00:17 +0100</pubDate>
      <guid>http://programmer.ie/books/context/17-chapter/</guid>
      <description>&lt;p&gt;An agent starts a routine task with fifteen integrations connected: file tools, shell, search, web, database, issue tracker, chat, calendar, drive, deployment, monitoring. Before it reads a single project file, tens of thousands of tokens of capability descriptions have already entered its context — names, descriptions, schemas for operations it will never call. Then it runs one search, and 40,000 tokens of matches flood the window for a question answerable from twelve lines. The task fails twice before it begins: once at the price of knowing what it could do, once at the price of seeing what it did. Both prices were design choices. This chapter prices them.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
