<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Agents on Blog | Tomáš Tomeček</title>
    <link>https://blog.tomecek.net/tags/agents/</link>
    <description>Recent content in Agents on Blog | Tomáš Tomeček</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 14 May 2026 08:19:00 +0200</lastBuildDate><atom:link href="https://blog.tomecek.net/tags/agents/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Deploying agents to OpenShift, again (part 2)</title>
      <link>https://blog.tomecek.net/post/deploying-agents-openshift-2/</link>
      <pubDate>Thu, 14 May 2026 08:19:00 +0200</pubDate>
      
      <guid>https://blog.tomecek.net/post/deploying-agents-openshift-2/</guid>
      <description>&lt;p&gt;This is a follow-up to the &lt;a href=&#34;https://blog.tomecek.net/post/deploying-agents-openshift/&#34;&gt;previous article&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;I find it so funny that I estimated the test deployment at 3 story points; at this point I&amp;rsquo;m at like 40 with the amount of work I put into this.&lt;/p&gt;
&lt;p&gt;But thanks to Claude it&amp;rsquo;s pretty fast to diagnose and solve problems.&lt;/p&gt;
&lt;p&gt;This time I even let it run &lt;code&gt;oc&lt;/code&gt; commands, even &lt;code&gt;oc rsh&lt;/code&gt;, but I never allowed commands that would change things or write to remote services. Everything stayed local.&lt;/p&gt;
&lt;p&gt;Here comes Claude&amp;rsquo;s writeup.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Deploying agents to OpenShift, again (part 1)</title>
      <link>https://blog.tomecek.net/post/deploying-agents-openshift/</link>
      <pubDate>Mon, 27 Apr 2026 08:00:00 +0200</pubDate>
      
      <guid>https://blog.tomecek.net/post/deploying-agents-openshift/</guid>
      <description>&lt;p&gt;We have a set of agents to work on packages in RHEL and CentOS Stream: &lt;a href=&#34;https://github.com/packit/ai-workflows&#34;&gt;packit/ai-workflows&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;They were already running pretty well in an OpenShift cluster last fall. Now we switched clusters so I worked on deploying them, again.&lt;/p&gt;
&lt;img src=&#34;https://blog.tomecek.net/img/sunset2026.JPG&#34; style=&#34;width: 800px;&#34;&gt;</description>
    </item>
    
    <item>
      <title>Backporting code with Claude Code Opus 4.6</title>
      <link>https://blog.tomecek.net/post/claude-code-backporting-opus-4-6/</link>
      <pubDate>Thu, 19 Mar 2026 08:00:00 +0200</pubDate>
      
      <guid>https://blog.tomecek.net/post/claude-code-backporting-opus-4-6/</guid>
      <description>&lt;p&gt;In the Fall of 2025 we&amp;rsquo;ve experimented with AI agents backporting upstream patches to CentOS Stream. For more info feel free to read:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://blog.tomecek.net/post/agentic-ai-claude-sonnet-4-5/&#34;&gt;First test of Claude Sonnet 4.5 for an agent that backports a patch&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://blog.tomecek.net/post/more-reliable-agents/&#34;&gt;More reliable agents&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://blog.tomecek.net/post/backporting-with-coding-agents/&#34;&gt;Backporting upstream patches with Code Assistants&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;There was one backport that served as &amp;ldquo;the final boss&amp;rdquo;: CVE-2025-59375 in expat. The upstream fix has 19 commits and changes almost 1000 lines. The models back then couldn&amp;rsquo;t handle this for Stream 9 where the drift in code was severe. I recall the backporting process halting several times with a message saying &amp;ldquo;this is too complex, a human developer with an IDE should do this work&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;It&amp;rsquo;s March 2026, let&amp;rsquo;s try to do this with Claude Code, imperfect prompt, and Opus 4.6.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Trying Claude Code prompt injections (Feb 2026)</title>
      <link>https://blog.tomecek.net/post/claude-code-prompt-injection-feb-2026/</link>
      <pubDate>Fri, 06 Feb 2026 12:00:00 +0200</pubDate>
      
      <guid>https://blog.tomecek.net/post/claude-code-prompt-injection-feb-2026/</guid>
      <description>&lt;p&gt;For quite some time I&amp;rsquo;ve wanted to test how prone agentic tools are to prompt injection. Let&amp;rsquo;s go.&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;ll be using Claude Code 2.1.5, 4.5 Opus in various different sessions.&lt;/p&gt;
&lt;img src=&#34;https://blog.tomecek.net/img/moonjan2026.JPG&#34; style=&#34;width: 800px;&#34;&gt;</description>
    </item>
    
    <item>
      <title>Ambient Code followup: PR merged</title>
      <link>https://blog.tomecek.net/post/ambient-code-merged/</link>
      <pubDate>Mon, 19 Jan 2026 09:00:00 +0200</pubDate>
      
      <guid>https://blog.tomecek.net/post/ambient-code-merged/</guid>
      <description>&lt;p&gt;This is a followup to &lt;a href=&#34;https://blog.tomecek.net/post/ambient-code/&#34;&gt;my previous post about how I tried Ambient Code&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;TL;DR: &lt;a href=&#34;https://github.com/packit/specfile/pull/508&#34;&gt;I opened a PR (#specfile/508)&lt;/a&gt; and had to take over in the end.&lt;/p&gt;
&lt;img src=&#34;https://blog.tomecek.net/img/ice.JPG&#34; style=&#34;width: 640px;&#34;&gt;
&lt;h2 id=&#34;where-did-we-end&#34;&gt;Where did we end?&lt;/h2&gt;
&lt;p&gt;Claude Code proposed a solid implementation plan to us, Stella (the staff engineer agent) approved it.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Ambient Code: first impressions</title>
      <link>https://blog.tomecek.net/post/ambient-code/</link>
      <pubDate>Mon, 12 Jan 2026 19:00:00 +0200</pubDate>
      
      <guid>https://blog.tomecek.net/post/ambient-code/</guid>
      <description>Ambient Code is a platform (not covered here) and a collection of AI coding agents and workflows designed to help with software development. I decided to give it a shot and see how well their agents can analyze and contribute to one of our projects in Packit org.
The first tool we are going to use is called agentready. It checks how well a project is maintained and suited for AI-assisted development.</description>
    </item>
    
    <item>
      <title>First test of Claude Sonnet 4.5 for an agent that backports a patch for an RPM</title>
      <link>https://blog.tomecek.net/post/agentic-ai-claude-sonnet-4-5/</link>
      <pubDate>Mon, 06 Oct 2025 08:00:00 +0200</pubDate>
      
      <guid>https://blog.tomecek.net/post/agentic-ai-claude-sonnet-4-5/</guid>
      <description>&lt;p&gt;One of the daily tasks we have when developing AI agents is to review their
runs. We have to read dozens of decisions so we can evaluate if the agents did
the right thing. If not, we have to adjust our user prompts, system prompts, and
tools.&lt;/p&gt;
&lt;p&gt;Let&amp;rsquo;s review how Sonnet 4.5 performs while backporting a complex patch
(with multiple conflicts).&lt;/p&gt;
&lt;img src=&#34;https://blog.tomecek.net/img/mushroom-2025.png&#34; style=&#34;width: 800px;&#34;&gt;</description>
    </item>
    
  </channel>
</rss>
