<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AI on cttech.io</title><link>https://cttech.io/tags/ai/</link><description>Recent content in AI on cttech.io</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 17 Aug 2026 10:00:00 +0000</lastBuildDate><atom:link href="https://cttech.io/tags/ai/index.xml" rel="self" type="application/rss+xml"/><item><title>Using AI to Find and Fix a Real Bug in Bitwarden</title><link>https://cttech.io/blog/fixing-a-bitwarden-bug-with-ai/</link><pubDate>Mon, 17 Aug 2026 10:00:00 +0000</pubDate><guid>https://cttech.io/blog/fixing-a-bitwarden-bug-with-ai/</guid><description>&lt;p&gt;I run my own self-hosted &lt;a href="https://bitwarden.com/"&gt;Bitwarden&lt;/a&gt; server. It holds every password I have, so I keep it patched and don&amp;rsquo;t take chances with it. A couple of weeks ago, gone 9pm, about to call it a day, a routine update went sideways: a crash, a couple of hours hunched over a stack trace in someone else&amp;rsquo;s source code, and eventually a pull request against Bitwarden&amp;rsquo;s official repository fixing a genuine bug.&lt;/p&gt;</description></item></channel></rss>