<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Tools on Sentinel</title><link>https://sentinel-blog.cherrypod.org/tags/tools/</link><description>Recent content in Tools on Sentinel</description><image><title>Sentinel</title><url>https://sentinel-blog.cherrypod.org/images/social-preview.png</url><link>https://sentinel-blog.cherrypod.org/images/social-preview.png</link></image><generator>Hugo -- 0.147.0</generator><language>en-gb</language><lastBuildDate>Sat, 21 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://sentinel-blog.cherrypod.org/tags/tools/index.xml" rel="self" type="application/rss+xml"/><item><title>Part 52: The Refactor</title><link>https://sentinel-blog.cherrypod.org/posts/52-the-refactor/</link><pubDate>Sat, 21 Feb 2026 00:00:00 +0000</pubDate><guid>https://sentinel-blog.cherrypod.org/posts/52-the-refactor/</guid><description>The codebase had grown fast. Features landed, bugs got fixed, new capabilities kept shipping. Then a structural audit revealed what that pace had cost: god files, god functions, and a growing maintenance burden.</description></item><item><title>Part 50: Pictures, Videos, Documents</title><link>https://sentinel-blog.cherrypod.org/posts/50-attachment-pipeline/</link><pubDate>Thu, 19 Feb 2026 00:00:00 +0000</pubDate><guid>https://sentinel-blog.cherrypod.org/posts/50-attachment-pipeline/</guid><description>Sentinel could generate code, build websites, write files. But every piece of content was synthetic — generated from scratch by an LLM. What if it could use real photos, real videos, real documents?</description></item><item><title>Part 49: Real-World Data</title><link>https://sentinel-blog.cherrypod.org/posts/49-weather-crypto-tools/</link><pubDate>Wed, 18 Feb 2026 00:00:00 +0000</pubDate><guid>https://sentinel-blog.cherrypod.org/posts/49-weather-crypto-tools/</guid><description>Sentinel could browse the web. It could read files and write code. But it couldn&amp;rsquo;t answer &amp;lsquo;what&amp;rsquo;s the weather?&amp;rsquo; without fabricating something. Time to give it real data backends.</description></item><item><title>Part 48: Named Anchors</title><link>https://sentinel-blog.cherrypod.org/posts/48-anchor-allocator/</link><pubDate>Tue, 17 Feb 2026 00:00:00 +0000</pubDate><guid>https://sentinel-blog.cherrypod.org/posts/48-anchor-allocator/</guid><description>file_patch needs the planner to find a unique anchor string in existing code. The planner is bad at this. What if the system placed named markers instead?</description></item><item><title>Part 47: Wrong Language, Wrong File</title><link>https://sentinel-blog.cherrypod.org/posts/47-cross-language-fixer/</link><pubDate>Mon, 16 Feb 2026 00:00:00 +0000</pubDate><guid>https://sentinel-blog.cherrypod.org/posts/47-cross-language-fixer/</guid><description>LLMs don&amp;rsquo;t always respect file boundaries. Raw CSS lands in HTML files, JavaScript appears without script tags. Building a detector to catch it.</description></item><item><title>Part 42: Building Websites</title><link>https://sentinel-blog.cherrypod.org/posts/42-building-websites/</link><pubDate>Wed, 11 Feb 2026 00:00:00 +0000</pubDate><guid>https://sentinel-blog.cherrypod.org/posts/42-building-websites/</guid><description>New planner, new classifier, new patching tool. Putting it all together to iteratively build and modify websites through conversation.</description></item><item><title>Part 41: file_patch</title><link>https://sentinel-blog.cherrypod.org/posts/41-file-patch/</link><pubDate>Tue, 10 Feb 2026 00:00:00 +0000</pubDate><guid>https://sentinel-blog.cherrypod.org/posts/41-file-patch/</guid><description>Full-file regeneration breaks at scale. The new tool generates only the changed fragments and splices them deterministically.</description></item></channel></rss>