<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Claude Code on bradleycarey.com</title>
    <link>https://bradleycarey.com/tags/claude-code/</link>
    <description>Recent content in Claude Code on bradleycarey.com</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Fri, 13 Mar 2026 19:46:37 -0400</lastBuildDate>
    <atom:link href="https://bradleycarey.com/tags/claude-code/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>I Built a Full CLI for a Legacy Web App in One Afternoon (with AI)</title>
      <link>https://bradleycarey.com/posts/building-a-cli-for-a-legacy-app-with-ai/</link>
      <pubDate>Fri, 13 Mar 2026 12:00:00 -0400</pubDate>
      <guid>https://bradleycarey.com/posts/building-a-cli-for-a-legacy-app-with-ai/</guid>
      <description>&lt;p&gt;Our platform has been around for nearly two decades. The backend is a sprawl of three separate HTTP services: a legacy REST API (v1), a newer REST API (v2), and an Elasticsearch-backed search service. They share a JWT token but have different base URLs, different conventions, and different quirks. There&amp;rsquo;s no unified CLI. If you want to poke at the API, you open Swagger, copy a Bearer token, and start curling.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
