lucasrosati

Claude Code Memory Setup — Data skill for Claude Code

Data community

Up to 71.5x fewer tokens per session on Claude Code with Obsidian + Graphify.

How to install Claude Code Memory Setup

This entry records only its repository, not the path inside it, so there is no exact command to give. Open lucasrosati/claude-code-memory-setup and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Claude Code Memory Setup does

Up to 71.5x fewer tokens per session on Claude Code with Obsidian + Graphify. Persistent memory, codebase knowledge graphs, and chat import pipeline. 🇧🇷 PT-BR included.

Alternatives in Data

  • OpenViking — Self-evolving Context Database for AI Agents 33.3k ★
  • LLM Redteam — LLM red-team corpus runner — fires categorized prompt-injection / jailbreak / system-prompt-leak / data-exfil 4.5k ★
  • Opencode Mem — OpenCode plugin that gives coding agents persistent memory using local vector database 1.5k ★

README

Claude Code + Obsidian + Graphify: The Definitive Guide to Token Savings & Persistent Memory

**71.5x fewer tokens per session** with Graphify + **permanent memory across sessions** with Obsidian Zettelkasten.

A complete setup to turn Claude Code into an agent with long-term memory and full codebase awareness — without wasting tokens re-reading files.

🇧🇷 [Leia em Português](./README.pt-BR.md)


Table of Contents

  1. The Problem
  2. The Solution (Overview)
  3. Part 1 — Obsidian as Persistent Memory
  4. Part 2 — Chat Import Pipeline
  5. Part 3 — Graphify (Codebase Knowledge Graph)
  6. Part 4 — Complete Workflow
  7. Real Results
  8. Troubleshooting

The Problem

When working with Claude Code, two problems silently eat your tokens:

**Problem 1 — Amnesia between sessions.** Every time you open a new session, you have to re-explain your project: stack, past decisions, current bugs, what's left to do. Claude Code remembers nothing from the previous session.

**Problem 2 — Codebase re-reading.** Claude Code re-reads all your project files every session to understand the structure. A project with ~40 files burns ~20,000 tokens just for Claude to orient itself — before you even ask a question. If you run 10 sessions a day, that's **200,000 wasted tokens**.


The Solution (Overview)

Two complementary systems, each solving a different problem:

Layer Tool Problem Solved Cost
Project memory Obsidian Zettelkasten Amnesia between sessions Free
Code map Graphify Codebase re-reading Free (AST mode)
Conversation history Import pipeline Lost chat insights Free
Continuity /resume and /save commands Picking up where you left off Free

Obsidian