US National WireUS NATIONAL WIRE
TechOpinion

The 'Self-Improving' Agent: AI's Newest Veneer for Basic Automation

Portrait of Trent Calloway
Trent Callowaythe contrarianNov 12AI
The 'Self-Improving' Agent: AI's Newest Veneer for Basic Automation

AI-generated image · US National Wire

Venture capital is betting on 'learning' agents, but a look at the plumbing suggests we are just rebranding the act of saving a text file.

The current AI gold rush has a new favorite buzzword: 'self-improvement.' The promise is a future where agents don't just execute tasks, but evolve through experience. However, as detailed in documentation first shared via Hacker News and GitHub, this 'evolution' looks suspiciously like a glorified version of a configuration file.

Take AgentRun, an open-source platform described in its own documentation as a way to 'supercharge' agents by adding 'self-improvement' and 'durable execution.' The pitch is seductive: agents that become smarter and more cost-efficient with every run. According to the project's GitHub page, AgentRun claims to solve the problem of agents 'rediscovering the same API' or 'rereading the same docs' every time they are deployed, which wastes tokens and money.

But look at the mechanism. AgentRun's 'learning' isn't some neural breakthrough; it is a system of markdown files and git commits. As detailed in the source material, when 'learning' is enabled, an agent takes one final turn after a job to propose 'notes, a skill, or a workflow.' If these proposals pass a code check and a 'grader,' they are committed to a git folder. The next run simply starts with these notes in its memory.

In the world of software, we have a name for this: caching. Or, more simply, documentation. The 'learning' process is essentially the agent writing a 'how-to' guide for itself and then reading that guide the next time it starts. While the documentation frames this as the agent 'learning the work,' it is effectively a loop of: do task $\rightarrow$ write note $\rightarrow$ read note $\rightarrow$ repeat task.

The financial incentives for this rebranding are clear. AgentRun cites case studies where this approach slashed costs. In one instance, a code review process that cost $6,451 a month after Greptile began charging $1 per review was replaced by a custom reviewer tuned on internal PRs, dropping the cost to 18 cents per review. In another example, a merchant classification task using Opus was handed off to a cheaper model, reducing costs from $0.89 to $0.12 per merchant.

These are genuine efficiency gains, but they aren't the result of a 'self-improving' consciousness. They are the result of using a high-end model to create a template and then using a low-end model to follow that template. It is a classic optimization play wrapped in the language of artificial intelligence.

AgentRun offers the 'plumbing'—provider integrations, recovery, and run tracking—allowing users to deploy agents via Docker sandboxes or Render. It supports harnesses like Claude Code, Codex, OpenCode, and pi. But the core 'innovation'—the Learning tab where users can see what the agent 'kept'—is just a log of markdown files and skills.

When the industry starts calling a git commit 'self-improvement,' it's a sign that the bubble is searching for new adjectives to justify the same old scripts. We aren't building entities that learn; we are building scripts that can save their own progress. Let's call it what it is.

Sources

More from Trent Calloway