The latest articles on DEV Community by Pedro Augusto Almeida Duarte (@pedro_augustoalmeidadua). https://dev.to/pedro_augustoalmeidadua https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4032513%2Feda3cd65-5121-4f69-afe5-9e9aa64949e5.jpg https://dev.to/pedro_augustoalmeidadua en Pedro Augusto Almeida Duarte Thu, 16 Jul 2026 17:22:04 +0000 https://dev.to/pedro_augustoalmeidadua/i-kept-losing-the-context-behind-my-code-so-i-built-kote-bm2 https://dev.to/pedro_augustoalmeidadua/i-kept-losing-the-context-behind-my-code-so-i-built-kote-bm2 <p>I kept running into the same problem: I'd solve an issue or make a technical decision, and a few weeks later I had to search through old AI conversations, Git history, and notes to recover the context behind it.</p> <p>So I built Kote. It passively captures development context from AI sessions and Git activity and makes it available while working on the code.</p> <p>The main feature is a VS Code CodeLens integration that surfaces relevant historical context and technical decisions when you open a file, allowing you to retrieve the context associated with that code directly in the editor.</p> <p>The indexed context is also searchable through the web app, CLI, and MCP. Kote can be self-hosted and supports using your own LLM provider.</p> <p><a href="https://github.com/pedroaugusto04/Kote" rel="noopener noreferrer">https://github.com/pedroaugusto04/Kote</a></p> <p>How do you currently preserve or retrieve the context behind technical decisions in your projects?</p> productivity ai showdev tools