<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ai-Tools on aeshift</title>
    <link>https://aeshift.com/tags/ai-tools/</link>
    <description>Recent content in Ai-Tools on aeshift</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>&amp;copy; 2026 [Dachary Carey](https://dacharycarey.com) - with agent assistance · Part of the [Agent Ecosystem Research Program](https://agentecosystem.dev)</copyright>
    <lastBuildDate>Sun, 22 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aeshift.com/tags/ai-tools/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Sashiko shows AI code review works by doing less, not more</title>
      <link>https://aeshift.com/posts/2026-03-22-sashiko-ai-code-review-system-for-the-linux-kernel-spots-bugs-humans-miss/</link>
      <pubDate>Sun, 22 Mar 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aeshift.com/posts/2026-03-22-sashiko-ai-code-review-system-for-the-linux-kernel-spots-bugs-humans-miss/</guid>
      <description>&lt;p&gt;If you want LLMs in production software workflows, &lt;a href=&#34;https://github.com/sashiko-dev/sashiko&#34;  target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;Sashiko&lt;/a&gt;, makes the argument that review is the place to start, not generation. An engineer at Google is putting that theory to the test on the Linux kernel. The early numbers are interesting. Whether they hold up under scrutiny is less clear.&lt;/p&gt;&#xA;&lt;p&gt;Roman Gushchin&amp;rsquo;s headline stat: Sashiko caught 53% of bugs in an unfiltered set of 1,000 recent upstream kernel issues (identified by &lt;code&gt;Fixes:&lt;/code&gt; tags), all of which had been missed by human reviewers. That&amp;rsquo;s not a claim of superhuman code understanding. It&amp;rsquo;s a claim about coverage, specifically incremental coverage on the failure mode kernel maintainers care about most: regressions that make it into mainline.&lt;/p&gt;</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://aeshift.com/posts/2026-03-22-sashiko-ai-code-review-system-for-the-linux-kernel-spots-bugs-humans-miss/feature.jpg" />
    </item>
    
    <item>
      <title>The Pentagon Just Made AI Provider Lock-in an Existential Risk</title>
      <link>https://aeshift.com/posts/2026-03-10-anthropic-sues-pentagon-over-alleged-ai-blacklist-on-claude/</link>
      <pubDate>Tue, 10 Mar 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aeshift.com/posts/2026-03-10-anthropic-sues-pentagon-over-alleged-ai-blacklist-on-claude/</guid>
      <description>&lt;p&gt;Anthropic suing the Pentagon isn&amp;rsquo;t just a DC food fight. It&amp;rsquo;s a warning shot for anyone building developer workflows on top of a single model vendor: your &amp;ldquo;agent stack&amp;rdquo; is now a supply-chain dependency, and the government is signaling it wants override rights on how that dependency is allowed to behave.&lt;/p&gt;&#xA;&lt;p&gt;But the part that matters for practitioners isn&amp;rsquo;t the First Amendment framing. It&amp;rsquo;s the mechanism. Defense Secretary Pete Hegseth slapped a &lt;a href=&#34;https://vechron.com/2026/03/anthropic-files-lawsuit-against-pentagon-over-ai-blacklist-and-claude-restrictions/&#34;  target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;&amp;ldquo;national security supply-chain risk&amp;rdquo; designation&lt;/a&gt; on Anthropic after months of contentious talks broke down over two red lines: Anthropic refused to remove safety guardrails preventing Claude&amp;rsquo;s use for autonomous weapons and mass surveillance of US citizens. That&amp;rsquo;s not procurement as usual. It&amp;rsquo;s the customer saying: we don&amp;rsquo;t just buy your tool; we set the policy layer inside it.&lt;/p&gt;</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://aeshift.com/posts/2026-03-10-anthropic-sues-pentagon-over-alleged-ai-blacklist-on-claude/feature.jpg" />
    </item>
    
  </channel>
</rss>
