<?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 Jason Craft</title><link>https://www.jasoncraft.org/workbench/tags/claude-code/</link><description>Recent content in Claude-Code on Jason Craft</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 08 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.jasoncraft.org/workbench/tags/claude-code/index.xml" rel="self" type="application/rss+xml"/><item><title>Co-Writing a Novel With an Agent: Style Engineering</title><link>https://www.jasoncraft.org/workbench/posts/03-style-engineering/</link><pubDate>Wed, 08 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.jasoncraft.org/workbench/posts/03-style-engineering/</guid><description>&lt;p&gt;LLM-generated text has some well-documented tics you&amp;rsquo;ve probably noticed. You might just understand them subconsciously, although nowadays there are memes that call them out. By default, the prose is passable, if not inspiring. It&amp;rsquo;s also weirdly uniform, and it has habits.&lt;/p&gt;
&lt;p&gt;This is the third post in a series about co-writing a &amp;ldquo;meganovel&amp;rdquo; (targeting 1,000,000 words or more) with an AI agent. The &lt;a href="https://www.jasoncraft.org/workbench/posts/01-context-management/"&gt;first&lt;/a&gt; covers the context management infrastructure. The &lt;a href="https://www.jasoncraft.org/workbench/posts/02-showrunner-model/"&gt;second&lt;/a&gt; covers the collaboration model and planning process. This one is about the output itself: what&amp;rsquo;s wrong with the robot&amp;rsquo;s prose defaults, and the system I&amp;rsquo;ve built to fight them.&lt;/p&gt;</description></item><item><title>Co-Writing a Novel With an Agent: The Showrunner Model</title><link>https://www.jasoncraft.org/workbench/posts/02-showrunner-model/</link><pubDate>Mon, 30 Mar 2026 00:00:00 +0000</pubDate><guid>https://www.jasoncraft.org/workbench/posts/02-showrunner-model/</guid><description>&lt;p&gt;This is the second post in a series about the systems I&amp;rsquo;ve built to co-write a &amp;ldquo;meganovel&amp;rdquo; (targeting 1,000,000 words or more) with an AI agent. The &lt;a href="https://www.jasoncraft.org/workbench/posts/01-context-management/"&gt;first post&lt;/a&gt; covers the context management problem and the search/MCP tooling I built to solve it. This one is about how we plan together, how I think about the collaboration, and the architectural contract that keeps the robot from surfacing things it shouldn&amp;rsquo;t.&lt;/p&gt;
&lt;p&gt;If you&amp;rsquo;ve used an agentic coding tool, you probably have picked up the flow of gathering context, building a structured understanding of the problem, producing a spec, then letting the agent execute autonomously from the spec. I use the same process to write chapters of a novel. The &amp;ldquo;problem&amp;rdquo; is a chapter. The &amp;ldquo;spec&amp;rdquo; is a beat sheet with dialogue intent and character notes. It&amp;rsquo;s a little more fun than a software spec (although some engineers might say the opposite), but it&amp;rsquo;s more the same than not.&lt;/p&gt;</description></item><item><title>Co-Writing a Novel With an Agent: Context Management at Scale</title><link>https://www.jasoncraft.org/workbench/posts/01-context-management/</link><pubDate>Sun, 22 Mar 2026 00:00:00 +0000</pubDate><guid>https://www.jasoncraft.org/workbench/posts/01-context-management/</guid><description>&lt;p&gt;I&amp;rsquo;ve been writing a novel with Claude for three months. The manuscript and supporting materials total over 626,000 words across 31 sequences and 200 files. (Which means I left behind both &lt;em&gt;Infinite Jest&lt;/em&gt; and &lt;em&gt;War and Peace&lt;/em&gt; word counts a little while ago.) I have enough plot runway to get to 1,000,000 words, easy, and I plan to keep going from there.&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt; There are 50 reference documents, 12 scaffolding files, and 716 commits. The agent generates the prose. I provide the creative vision and plan the narrative. Together, we edit the output and build the systems that make generation possible.&lt;/p&gt;</description></item><item><title>Agentic Development: All In</title><link>https://www.jasoncraft.org/workbench/posts/agentic-development-all-in/</link><pubDate>Sun, 15 Mar 2026 00:00:00 +0000</pubDate><guid>https://www.jasoncraft.org/workbench/posts/agentic-development-all-in/</guid><description>&lt;p&gt;For the past five months, I&amp;rsquo;ve been co-leading development of an enterprise platform where nearly 100% of the code is written by AI coding agents. This isn&amp;rsquo;t POC or experiment mode. We&amp;rsquo;re adopting agent generation as a production engineering practice for a first-class product.&lt;/p&gt;
&lt;p&gt;We were lucky in our timing. The models keep getting meaningfully better: September 2025, November, again this year. It feels like we started at the point right when the models became viable for this sort of operation. We aren&amp;rsquo;t vibe coding and we&amp;rsquo;re not hand-writing with autocomplete. It&amp;rsquo;s a different relationship between the engineer and the code.&lt;/p&gt;</description></item></channel></rss>