<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Agents on Big Muddy</title><link>https://muddy.jprs.me/tags/agents/</link><description>Recent content in Agents on Big Muddy</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sat, 04 Apr 2026 23:59:00 -0400</lastBuildDate><atom:link href="https://muddy.jprs.me/tags/agents/index.xml" rel="self" type="application/rss+xml"/><item><title>The definition of "agent"</title><link>https://muddy.jprs.me/notes/2026-04-04-the-definition-of-agent/</link><pubDate>Sat, 04 Apr 2026 23:59:00 -0400</pubDate><guid>https://muddy.jprs.me/notes/2026-04-04-the-definition-of-agent/</guid><description>&lt;p&gt;An interesting exchange between &lt;a href="https://x.com/gvanrossum/status/2039045160156426463"&gt;Guido van Rossum&lt;/a&gt; and &lt;a href="https://x.com/karpathy/status/2039054981719089202"&gt;Andrej Karpathy&lt;/a&gt; a few days ago on Twitter:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Guido van Rossum:&lt;/strong&gt;
I think I finally understand what an agent is. It&amp;rsquo;s a prompt (or several), skills, and tools. Did I get this right?&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Andrej Karpathy&lt;/strong&gt;:
LLM = CPU (data: tokens not bytes, dynamics: statistical and vague not deterministic and precise)
Agent = operating system kernel&lt;/p&gt;
&lt;/blockquote&gt;</description></item><item><title>Testing ZeroClaw, Part 2.5: ZeroClaw is alive!</title><link>https://muddy.jprs.me/notes/2026-04-01-testing-zeroclaw-part-2-5-zeroclaw-is-alive/</link><pubDate>Wed, 01 Apr 2026 23:59:00 -0400</pubDate><guid>https://muddy.jprs.me/notes/2026-04-01-testing-zeroclaw-part-2-5-zeroclaw-is-alive/</guid><description>&lt;p&gt;&lt;a href="https://muddy.jprs.me/notes/2026-03-31-testing-zeroclaw-part-2-zeroclaw-is-dead/"&gt;Yesterday&lt;/a&gt;, I wrote about how the &lt;a href="https://github.com/zeroclaw-labs/zeroclaw"&gt;ZeroClaw GitHub repository&lt;/a&gt; had been down for two days with little explanation. Earlier today, the project provided a little more information on &lt;a href="https://x.com/zeroclawlabs/status/2039419021494264055"&gt;Twitter&lt;/a&gt;:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;They flagged our org which is why we’re down. Code is safe and we’re still working, just waiting for @github&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Since March 30 (the day after their repo started 404ing), they project has been promising a blog post to explain the situation. As of now, &lt;a href="https://www.zeroclawlabs.ai/blog"&gt;that post is now available&lt;/a&gt;:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Over the past few days, a maintainer used aggressive AI automation to review and merge PRs:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Merges went through that shouldn&amp;rsquo;t have.&lt;/li&gt;
&lt;li&gt;In the process of trying to undo the damage, the maintainer&amp;rsquo;s GitHub account was flagged, which triggered enforcement actions on the ZeroClaw org itself.&lt;/li&gt;
&lt;li&gt;That maintainer has been removed from the project.&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;
&lt;p&gt;This sounds strikingly similar to the incident that &lt;a href="https://web.archive.org/web/20260331214457/https://t.me/ZeroClawLabs/11"&gt;occurred about a month ago&lt;/a&gt;, which I also mentioned in yesterday&amp;rsquo;s post:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Earlier today, during routine maintenance, the visibility of the ‎`zeroclaw-labs/zeroclaw` repository was accidentally changed from public to private and was later restored to public.&lt;/p&gt;
&lt;p&gt;After reviewing the GitHub API audit logs and collecting detailed feedback from our engineers, we confirmed that the incident was caused by improper use of an AI agent tool during maintenance.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Obviously, the use agentic workflows in open source projects is an emerging field where best practices have not yet been established. The case of ZeroClaw should be a warning to other projects to keep human review in the loop, or at least to limit the autonomy of agents when a project has numerous contributors. As they say in their blog post:&lt;/p&gt;</description></item><item><title>Testing ZeroClaw, Part 2: ZeroClaw is dead?</title><link>https://muddy.jprs.me/notes/2026-03-31-testing-zeroclaw-part-2-zeroclaw-is-dead/</link><pubDate>Tue, 31 Mar 2026 20:57:00 -0400</pubDate><guid>https://muddy.jprs.me/notes/2026-03-31-testing-zeroclaw-part-2-zeroclaw-is-dead/</guid><description>&lt;p&gt;&lt;a href="https://muddy.jprs.me/notes/2026-03-02-testing-zeroclaw-part-1-setup/"&gt;Earlier this month&lt;/a&gt;, I wrote about setting up one of the many lightweight OpenClaw alternatives, namely ZeroClaw. I had some issues with initial setup, but I got to the point where I could talk with my bot over Telegram.&lt;/p&gt;
&lt;p&gt;Some of my initial enthusiasm for ZeroClaw was dampened by the divergence between the docs and the features available in the release build. The release build was quite out of date due to the breakneck pace of development. In the week or two following my initial setup, the release build pipeline was broken, so even when they released a new tag, there were no new precompiled binaries available. Being forced to compile the Rust binary yourself kind of goes against the project&amp;rsquo;s philosophy of ultra-low resource consumption.&lt;/p&gt;
&lt;p&gt;They eventually fixed the release pipeline and I started casually working on a system where I could send notes and ideas for blog posts to my bot through Telegram and have it turn them into structured Markdown files.&lt;/p&gt;
&lt;p&gt;But two days ago (March 29), I noticed that the ZeroClaw &lt;a href="https://github.com/zeroclaw-labs/zeroclaw"&gt;GitHub repo&lt;/a&gt; was 404ing. On the same day, the project posted the following on &lt;a href="https://x.com/zeroclawlabs/status/2038407120312299524"&gt;Twitter&lt;/a&gt;:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Our GitHub repo is currently returning a 404 for some users. We&amp;rsquo;re aware and actively investigating. The repo is public and all code is safe.&lt;/p&gt;</description></item><item><title>Testing ZeroClaw, Part 1: Setup</title><link>https://muddy.jprs.me/notes/2026-03-02-testing-zeroclaw-part-1-setup/</link><pubDate>Mon, 02 Mar 2026 19:15:00 -0500</pubDate><guid>https://muddy.jprs.me/notes/2026-03-02-testing-zeroclaw-part-1-setup/</guid><description>&lt;p&gt;As mentioned &lt;a href="https://muddy.jprs.me/links/2026-02-24-comparing-the-claw-like-agent-ecosystem/"&gt;last week&lt;/a&gt;, I&amp;rsquo;ve been meaning to test out a personal agent from the Claw-like ecosystem. I settled on testing out &lt;a href="https://github.com/zeroclaw-labs/zeroclaw"&gt;Zeroclaw&lt;/a&gt;, a popular and lightweight OpenClaw alternative that should run well on my Raspberry Pi 4 4GB.&lt;/p&gt;
&lt;p&gt;I wanted to harden my setup as much as possible and opted to running everything in Docker. I started with the &lt;a href="https://github.com/zeroclaw-labs/zeroclaw/blob/main/docker-compose.yml"&gt;official Docker compose file&lt;/a&gt; and added my OpenRouter key. I brought up the pre-built container image and tried sending the basic &amp;ldquo;Hello&amp;rdquo; message to the agent using the CLI. However, I got error because the automatically generated config file defaulted to a version of Claude Sonnet 4 that wasn&amp;rsquo;t available on OpenRouter. I switched to &lt;code&gt;claude-sonnet-4.6&lt;/code&gt; and then &lt;code&gt;gpt-oss-20b&lt;/code&gt; (for &lt;em&gt;much&lt;/em&gt; cheaper testing).&lt;/p&gt;
&lt;p&gt;The Zeroclaw web gateway was a bit of a mess. Of the features I tried, only memory management and the basic status dashboard worked. Trying to talk to the agent through the web interface would give me a black screen (&lt;a href="https://www.reddit.com/r/ZeroClaw/comments/1rc525q/zeroclaw_web_issues/"&gt;here&amp;rsquo;s someone complaining about the same error&lt;/a&gt;). I&amp;rsquo;m still being charged for the tokens, though! The cost tracker always displayed zero, even as I sent CLI and Telegram messages (more on that soon). The configuration editor gave me an error and so did the diagnostics tool.&lt;/p&gt;
&lt;p&gt;The project docs/wiki were helpful for figuring things out, but development is running so far ahead of releases that a bunch of the features referred to aren&amp;rsquo;t available in the current stable version (v0.1.7, from last week). This includes getting and setting specific config options from the CLI and resetting the gateway pairing token. To use these features, you have to compile yourself.&lt;/p&gt;</description></item><item><title>Agentic engineering patterns</title><link>https://muddy.jprs.me/links/2026-02-25-agentic-engineering-patterns/</link><pubDate>Wed, 25 Feb 2026 16:15:00 -0500</pubDate><guid>https://muddy.jprs.me/links/2026-02-25-agentic-engineering-patterns/</guid><description>&lt;p&gt;Simon Willison is building a library of posts covering best practices for using agentic coding tools like Claude Code and OpenAI&amp;rsquo;s Codex. The existing articles cover test-driven development (red/green—ensure tests fail before the change and succeed after it) and AI-assisted code walkthroughs.&lt;/p&gt;</description></item><item><title>Comparing the Claw-like agent ecosystem</title><link>https://muddy.jprs.me/links/2026-02-24-comparing-the-claw-like-agent-ecosystem/</link><pubDate>Tue, 24 Feb 2026 22:44:00 -0500</pubDate><guid>https://muddy.jprs.me/links/2026-02-24-comparing-the-claw-like-agent-ecosystem/</guid><description>&lt;p&gt;Chrys Bader has created ClawCharts to track the popularity and growth of OpenClaw and its growing number of competitors.&lt;/p&gt;
&lt;p&gt;I have an unused Raspberry Pi 4 4GB that I&amp;rsquo;ve been meaning to test one of these Claw-like personal agents on (locked down to prevent the security nightmare scenarios we&amp;rsquo;ve seen play out since OpenClaw took off).&lt;/p&gt;
&lt;p&gt;OpenClaw is a bit of a resource hog (which is why so many people are running out to buy Mac Minis), so I&amp;rsquo;ve been looking at the list of lightweight competitors. There is no obvious reason to prefer one over the other, so I&amp;rsquo;ll probably go with the fast-growing &lt;a href="https://github.com/zeroclaw-labs/zeroclaw"&gt;ZeroClaw&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;ZeroClaw offers OAuth connectors for OpenAI and Anthropic subscription plans, but presently neither company is clear on whether this usage is permissible or not. Anthropic recently blew up the OpenClaw community by &lt;a href="https://web.archive.org/web/20260221222303/https://code.claude.com/docs/en/legal-and-compliance#authentication-and-credential-use"&gt;updating their docs&lt;/a&gt; to specifically ban using OAuth outside of Claude Code. An Anthropic employee &lt;a href="https://thenewstack.io/anthropic-agent-sdk-confusion/"&gt;partially walked this back on Twitter&lt;/a&gt;, but there is still no clear statement whether this use case is permitted. Regarding the use of OAuth from OpenAI for OpenClaw (specifically, GPT Codex), Peter Steinberger, creator of OpenClaw, &lt;a href="https://x.com/steipete/status/2024182608746217953"&gt;stated on Twitter&lt;/a&gt;: &amp;ldquo;that already works, OAI publicly said that&amp;rdquo;. No one can seem to find this public statement, but it&amp;rsquo;s worth noting that Steinberger himself is now an OpenAI employee. So, will you get banned for using your ChatGPT Plus/Pro or Claude Pro/Max subscriptions with OpenClaw? Nobody knows.&lt;/p&gt;</description></item></channel></rss>