GitMemo

Save AI conversations and notes into your Git repo.

6 followers

Save AI conversations and notes into your Git repo.

6 followers

GitMemo helps Claude Code & Cursor users save AI conversations, notes and work into a Git repo they own. It hooks into your editor to capture useful outputs as searchable Markdown in Git. Search everything later from CLI, MCP or Desktop. Built-in scratch notes, daily notes and docs. Local-first, remote sync optional. Set up once, then use /save. Desktop app available on macOS.

Interactive

Free

Launch tags:Productivity•Developer Tools•GitHub

Launch Team

Render Sandboxes: a computer for every agentGive every agent its own machine. Starts in under a second

Promoted

Maker

📌

Hey everyone! 👋 I built GitMemo because I kept losing useful AI conversations I wanted to reuse later. I use Claude Code and Cursor every day. During a session, I'd get valuable outputs — problem analysis, working solutions, code snippets, little decisions worth keeping. But once the session ended, they were buried in chat history or lost in the clipboard. A week later, I'd end up solving the same problem again. I tried saving things manually to note apps, but it never stuck. What I really wanted was simple: useful AI work should become searchable files in my own repo, not disappear into another hosted tool. So GitMemo is built for developers who live in Claude Code or Cursor and want their AI work — conversations, notes, decisions — to stay theirs, searchable and versioned in Git. It integrates with both editors through native instructions, hooks, and MCP, and saves conversations as local Markdown tracked by Git. Alongside that, it comes with built-in scratch notes, daily notes, and docs, plus full-text search across conversations, notes, and clipboard history — reachable from CLI, MCP, or the Desktop app. Setup is one command: `gitmemo init` → pick your editor → done. After that, `/save` inside Claude Code or Cursor is all you need. The goal is straightforward: your AI work shouldn't vanish after the session. It should stay searchable, versioned, and fully yours. Desktop ships for macOS, CLI works on macOS and Linux, clipboard capture is optional, remote Git sync is optional, and the whole thing is built in Rust and open source under MIT. Would love to hear how you're handling AI conversations today — especially if you also build with Claude Code or Cursor.

Report

7mo ago

Forum Threads

p/gitmemo

•

7mo ago

How do you manage your AI conversations and dev notes?

Hey everyone! I'm building GitMemo a tool that saves AI conversations (from Claude, ChatGPT, etc.) and personal notes directly into your Git repository as plain Markdown files. The problem I kept running into: I'd have an incredible debugging session with an AI, close the tab, and lose everything. Or I'd scatter notes across Notion, Apple Notes, and random .md files with no
single source of truth. GitMemo takes a different approach your knowledge stays in Git, versioned, searchable, and fully yours. No vendor lock-in, no proprietary format, no sync service. Just Markdown + Git. Curious to hear from this community:
- Where do you currently save useful AI conversations?
- Do you keep dev notes alongside your code, or in a separate tool?
- What's the biggest pain point in your current workflow? Would love your thoughts. We're launching soon and your feedback will directly shape the product!

View all