<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ax on Patrik Potocki</title><link>https://potocki.dev/tags/ax/</link><description>Recent content in Ax on Patrik Potocki</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 29 Apr 2026 09:10:58 +0200</lastBuildDate><atom:link href="https://potocki.dev/tags/ax/index.xml" rel="self" type="application/rss+xml"/><item><title>Agent-First: Designing for MCP and CLI as the Primary Surface</title><link>https://potocki.dev/posts/agent-first-designing-for-mcp-cli-as-the-primary-surface/</link><pubDate>Wed, 29 Apr 2026 00:00:00 +0000</pubDate><guid>https://potocki.dev/posts/agent-first-designing-for-mcp-cli-as-the-primary-surface/</guid><description>&lt;p>Most teams still design software like a human is going to click through it. They build the frontend first, treat the API as plumbing behind it, and bolt a CLI on at the end if anyone asks. That order made sense when the user was always a person.&lt;/p>
&lt;p>It doesn&amp;rsquo;t anymore. The fastest-growing user of any non-trivial software product right now is an agent — driving it through an API, an MCP server, or a CLI. If you accept that, the priority order has to flip.&lt;/p></description></item></channel></rss>