<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Qdrant on DevOpsTales</title>
    <link>https://devopstales.github.io/tags/qdrant/</link>
    <description>Recent content in Qdrant on DevOpsTales</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Sun, 05 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://devopstales.github.io/tags/qdrant/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Kilo Code: Mastering Codebase Indexing for Semantic AI Search</title>
      <link>https://devopstales.github.io/ai/kilo-code-series-12-codebase-indexing/</link>
      <pubDate>Sun, 05 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://devopstales.github.io/ai/kilo-code-series-12-codebase-indexing/</guid>
      <description>One of the most powerful features of Kilo Code is its ability to understand your entire codebase semantically—not just through keyword matching, but by grasping the actual meaning and relationships in your code.
</description>
      <enclosure url="https://devopstales.github.io/img/kilocode.webp" length="908" type="image/png" />
    </item>
    
    <item>
      <title>Kilo Code: Codebase Indexing with Nomic and Qdrant</title>
      <link>https://devopstales.github.io/ai/kilo-code-series-05-indexing/</link>
      <pubDate>Sun, 29 Mar 2026 00:00:00 +0000</pubDate>
      
      <guid>https://devopstales.github.io/ai/kilo-code-series-05-indexing/</guid>
      <description>In our previous post, we explored the different modes of Kilo Code. While these modes are powerful, their effectiveness depends on the quality of the context they can access.
</description>
      <enclosure url="https://devopstales.github.io/img/kilocode.webp" length="908" type="image/png" />
    </item>
    
  </channel>
</rss>
