<?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 Aleksandr Filippov</title><link>https://www.alexfeel.info/tags/claude-code/</link><description>Recent content in Claude-Code on Aleksandr Filippov</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 06 Jul 2026 09:25:56 +0300</lastBuildDate><atom:link href="https://www.alexfeel.info/tags/claude-code/index.xml" rel="self" type="application/rss+xml"/><item><title>Dynamic Workflows: When the Agent Writes Its Own Harness</title><link>https://www.alexfeel.info/blog/post-6/</link><pubDate>Mon, 06 Jul 2026 05:00:00 +0000</pubDate><guid>https://www.alexfeel.info/blog/post-6/</guid><description>For a few weeks now, Claude Code has been writing its own multi-agent harness for each task &amp;ndash; and it quietly retired the orchestration code I used to maintain by hand. Here is what changed, the patterns worth knowing, and the research idea I think sits underneath it.</description></item></channel></rss>