lucasrosati/claude-code-memory-setup

Coding · tested 2026-09-24 · by the Hlido desk, not the vendor

In short: A well-documented setup guide and toolchain for giving Claude Code persistent memory and codebase awareness via Obsidian + Graphify — high-value as a recipe, but it's a configuration playbook, not a product.

8 PASS · 2 FAIL of 10 public-surface claims

Quick answer

lucasrosati/claude-code-memory-setup scores 82/100 (STEADY) on Hlido’s independent, hands-on test (reviewed 2026-09-24). STEADY reflects a well-maintained, MIT-licensed, clearly documented and actively updated guide that solves recognised Claude Code problems. Pricing: Open source (free entry point documented).

This project packages a complete method for two real Claude Code pain points: amnesia between sessions and token waste from re-reading files. Its answer pairs Obsidian (as a Zettelkasten of "what was decided" — declarative memory) with Graphify (a codebase knowledge graph for "how the code is structured" — structural memory), plus a chat-import pipeline, and it headlines "up to 71.5x fewer tokens per session." As a guide it is genuinely useful and clearly written, bilingual (EN/PT-BR), MIT-licensed, and actively maintained, and it addresses problems every heavy Claude Code user recognises. The honest framing matters, though: this is a configuration playbook stitching third-party tools (Obsidian, Graphify) together, not a standalone application Hlido can run and measure. The eye-catching 71.5x figure is the author's, is best-case and workload-dependent, and was not benchmarked here. Its durability is also tied to the underlying tools staying compatible with Claude Code as that product evolves. For a developer willing to invest an afternoon in setup, the payoff is plausibly large; for someone wanting a one-click install, this isn't it.

Why STEADY

STEADY reflects a well-maintained, MIT-licensed, clearly documented and actively updated guide that solves recognised Claude Code problems. Not higher because it is a configuration playbook over third-party tools rather than a runnable product (limiting what Hlido can independently verify, medium confidence), and its headline token-saving claim is best-case, author-reported, and unmeasured here.

Public-surface checklist

What we saw

1 screenshot captured by the Hlido engine during the reviewed run (run-7a2089a0fb0d5e76-github-com). Our own captures — not vendor marketing material.

lucasrosati/claude-code-memory-setup — run screenshot 1 (home.png)
home.png

What it does well

What it fails at

Best for

  • Heavy Claude Code users willing to invest setup time for persistent memory and lower token use
  • Developers who already use or are open to Obsidian for a second brain
  • Teams standardising how they carry project context across AI-coding sessions
  • PT-BR-speaking developers wanting first-class localised guidance

Not recommended for

  • Users wanting a packaged, one-click product rather than a configuration playbook
  • Anyone unwilling to adopt Obsidian and Graphify as dependencies
  • Buyers who need the token-saving claim independently proven before investing setup time
  • Environments that can't rely on third-party tools tracking Claude Code changes

Pricing & access

Derived from Hlido-held evidence only (engine checklist + editorial text); quotes are verbatim from the scorecard; not vendor-supplied; re-derived daily. Verify current prices on the vendor's pricing page. Last verified 2026-07-16.

Related agents

Agent relevance

CLI

Agentic-Commerce Readiness 28/100 · SURFACE-ONLY

Independent readiness for agent delegation & transaction. How it’s scored · check live

A methodology for configuring Claude Code with Obsidian + Graphify for persistent memory and codebase awareness. Not a component agents call; rather, it shapes how a coding agent is set up. Value is in the workflow, not an API.

Agent-friendly score: 5/10

Evidence

scorecard.json · transparency passport · registry · methodology

More: compare agents · best of · developer tools · incident registry

Verdict by Hlido Editor, our automated editorial system · Method: public-surface+repo-health-tier-2+editorial-narrative-v2 · Methodology version 2026.09 ·

How this page was produced. The scores, claim verdicts and evidence come from automated hands-on testing of the product’s public surface. The written analysis is drafted by an AI system, and pages publish without a person reviewing each one. Hlido publishes this record and answers for it — tell us if anything here is wrong and we will correct it.

Embed this trust badge

Hlido trust score

Live, always-current independent score — free to embed on your site or README. No vendor pays for placement.

Markdown

[![Hlido trust score](https://hlido.eu/badge/lucasrosati-claude-code-memory-setup.svg)](https://hlido.eu/check/?agent=lucasrosati-claude-code-memory-setup)

HTML

<a href="https://hlido.eu/check/?agent=lucasrosati-claude-code-memory-setup"><img src="https://hlido.eu/badge/lucasrosati-claude-code-memory-setup.svg" alt="Hlido trust score"></a>