<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ai-Assistant on /var/log/janio</title><link>https://devops.sarmento.org/en/tags/ai-assistant/</link><description>Recent content in Ai-Assistant on /var/log/janio</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 18 Apr 2026 13:19:00 +0000</lastBuildDate><atom:link href="https://devops.sarmento.org/en/tags/ai-assistant/index.xml" rel="self" type="application/rss+xml"/><item><title>Hugin on steroids: tags, links and editing in one TUI</title><link>https://devops.sarmento.org/en/posts/hugin-on-steroids-tags-links-and-editing-in-one-tui/</link><pubDate>Sat, 18 Apr 2026 13:13:00 +0000</pubDate><guid>https://devops.sarmento.org/en/posts/hugin-on-steroids-tags-links-and-editing-in-one-tui/</guid><description>&lt;p&gt;In the &lt;a href="https://devops.sarmento.org/en/posts/hugin-tags-and-summaries-for-hugo-with-ai/"&gt;post about Hugin&lt;/a&gt; I introduced the tool I use to generate tags and summaries for my Hugo blogs. Two weeks later, in the &lt;a href="https://devops.sarmento.org/en/posts/munin-internal-links-for-hugo-with-ai/"&gt;post about Munin&lt;/a&gt;, I showed its sibling: a second program that discovers and inserts internal links between posts using embeddings and an LLM.&lt;/p&gt;
&lt;p&gt;Both worked well. Separately, they worked well.&lt;/p&gt;
&lt;h2 id="the-problem-with-having-two-programs"&gt;The problem with having two programs&lt;/h2&gt;
&lt;p&gt;In theory, splitting responsibilities between tools is good practice. In practice, the workflow for processing a new post looked like this: open Hugin, navigate to the post, generate tags, generate summary, close Hugin. Open Munin, wait for the embedding model to load, navigate to the same post, check existing links, generate link suggestions, apply. If you needed to fix a typo in the title that only showed up after reviewing the post in Hugin, close everything and open Pages CMS or vim.&lt;/p&gt;</description></item><item><title>Hugin: tags and summaries for Hugo with AI</title><link>https://devops.sarmento.org/en/posts/hugin-tags-and-summaries-for-hugo-with-ai/</link><pubDate>Fri, 17 Apr 2026 11:06:00 +0000</pubDate><guid>https://devops.sarmento.org/en/posts/hugin-tags-and-summaries-for-hugo-with-ai/</guid><description>&lt;p&gt;Anyone who maintains a &lt;a href="https://devops.sarmento.org/posts/why-leave-wordpress-and-what-to-build-instead-with-hugo-pages-cms-and-cloudflare/"&gt;static blog with Hugo&lt;/a&gt; knows there are two tasks nobody enjoys: classifying posts with tags and writing meta descriptions. These are the things you skip when publishing because the post is already done, the deploy is set up, and choosing between &amp;ldquo;selfhosted&amp;rdquo; and &amp;ldquo;self-hosted&amp;rdquo; isn&amp;rsquo;t exactly the best use of your time. The result is predictable: posts without tags, empty descriptions or ones copied from the first paragraph, and a taxonomy that hurts more than it helps.&lt;/p&gt;</description></item></channel></rss>