<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>agentty blog</title>
    <link>https://agentty.org/blog/</link>
    <atom:link href="https://agentty.org/blog/feed.xml" rel="self" type="application/rss+xml" />
    <description>Release notes, performance deep dives, and design notes from the agentty project — the native C++26 claude-code alternative.</description>
    <language>en-us</language>
    <lastBuildDate>Wed, 10 Jun 2026 00:00:00 GMT</lastBuildDate>
    <generator>agentty.org</generator>
    <item>
      <title>Implementing the Agent Client Protocol in C++: a codec is a fold, not a ritual</title>
      <link>https://agentty.org/blog/implementing-acp-in-cpp/</link>
      <guid isPermaLink="true">https://agentty.org/blog/implementing-acp-in-cpp/</guid>
      <pubDate>Wed, 10 Jun 2026 00:00:00 GMT</pubDate>
      <description>I wrote the first C++ implementation of the Agent Client Protocol — the thing that lets Zed drive Claude Code and Gemini. Most JSON-RPC libraries hand you stringly-typed blobs and a prayer. acp-cpp treats the protocol as what it actually is: a closed algebra of inductive types, where serialization is a fold over the type&apos;s shape and the compiler proves you handled every case. Here&apos;s the whole design, from the unit type up to the deferred-reply trick that keeps a single-reader transport from deadlocking mid-turn.</description>
      <author>noreply@agentty.org (agentty)</author>
      <category>c++</category><category>acp</category><category>protocol</category><category>deep-dive</category><category>design</category>
    </item>
    <item>
      <title>The C++ design of a terminal coding agent: a state machine that can&apos;t lie to you</title>
      <link>https://agentty.org/blog/cpp-design-of-a-terminal-agent/</link>
      <guid isPermaLink="true">https://agentty.org/blog/cpp-design-of-a-terminal-agent/</guid>
      <pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate>
      <description>An LLM agent loop looks like the worst possible fit for C++ — async, streaming, full of stringly-typed events. It is actually one of the best. Here&apos;s how agentty turns the whole app into a closed sum of events, a single std::visit reducer, and a permission matrix the compiler proves correct over all 48 cells.</description>
      <author>noreply@agentty.org (agentty)</author>
      <category>c++</category><category>architecture</category><category>deep-dive</category><category>design</category>
    </item>
    <item>
      <title>I rewrote the Claude terminal agent in C++ and it cold-starts 50× faster</title>
      <link>https://agentty.org/blog/why-cpp-coding-agent-50x-faster/</link>
      <guid isPermaLink="true">https://agentty.org/blog/why-cpp-coding-agent-50x-faster/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>claude-code spends ~150 ms and 222 MB of Node just to print its version. agentty is one 9.6 MB binary that does it in ~3 ms. Here&apos;s exactly where the time goes, why a coding agent is a surprisingly good fit for C++26, and the numbers you can reproduce yourself.</description>
      <author>noreply@agentty.org (agentty)</author>
      <category>performance</category><category>c++</category><category>deep-dive</category>
    </item>
    <item>
      <title>agentty 0.2.0 — run your terminal agent inside Zed</title>
      <link>https://agentty.org/blog/agentty-0-2-0-zed-acp/</link>
      <guid isPermaLink="true">https://agentty.org/blog/agentty-0-2-0-zed-acp/</guid>
      <pubDate>Sat, 06 Jun 2026 00:00:00 GMT</pubDate>
      <description>0.2.0 teaches agentty to speak the Agent Client Protocol, so the same engine that drives the TUI now drives a first-class agent panel inside Zed — streaming text, inline diffs, native permission prompts, and session reload.</description>
      <author>noreply@agentty.org (agentty)</author>
      <category>release</category><category>acp</category><category>zed</category>
    </item>
  </channel>
</rss>
