HN Showcase
Back to browse
GitHub Repository

A developer memory layer that automatically captures and organizes AI sessions, Git history, and development context into searchable knowledge.

3 starsTypeScript

Kote – Capture and reuse engineering context from AI chats and Git

by pedrodduarte·Jul 12, 2026·2 points·0 comments
Visit ProjectView on HN

AI Analysis

●●SolidShip ItBig Brain

Auto-capturing AI chat context alongside Git commits solves a real memory leak problem.

Strengths
  • •Integrates directly with VS Code to surface historical context while editing files.
  • •Supports self-hosting with custom LLM providers for privacy-conscious teams.
  • •Uniquely captures voice and text notes via WhatsApp into the same knowledge graph.
Weaknesses
  • •Fair-code license limits commercial use compared to fully open alternatives.
  • •Relies on specific AI assistant integrations that may change APIs frequently.
Target Audience

Software developers using AI coding assistants

Similar To

Obsidian · Mem · Sourcegraph Cody

Post Description

I kept running into the same problem: I'd solve something with the help of an AI assistant, spend time debugging an issue, or make an architectural decision... and a few weeks later I couldn't remember where that information was. Most of the time I simply didn't bother saving it anywhere.

So I built Kote to capture that context automatically instead of relying on me to document it.

Right now it can capture AI chats (Antigravity, Codex, Claude Code, OpenCode) from the VS Code extension or CLI, analyze Git pushes, retrieve historical context during Pull Requests, save quick text or voice notes through WhatsApp, and make everything searchable from the web app or directly from VS Code.

Kote can be self-hosted and works with your own LLM provider, though I've primarily tested it with Gemini.

I'm curious how other people handle this. Do you use another tool or workflow to preserve this kind of engineering context?

Similar Projects