I used Obsidian as a persistent brain for Claude Code and built a full open source tool over a weekend. happy to share the exact setup.
TL;DR Highlight
A development workflow sharing how someone used an Obsidian vault as Claude Code's persistent memory to ship an open-source tool in a weekend.
Who Should Read
Developers using Claude Code on long-term projects who need persistent context across sessions.
Core Mechanics
- By treating an Obsidian vault as a structured knowledge base, the developer gave Claude Code persistent memory of project decisions, architecture choices, and context that normally resets between sessions.
- The Obsidian vault structure (linked notes, tags, backlinks) maps well to how Claude Code consumes context — hierarchical and cross-referenced information is easier to navigate than flat documents.
- The workflow: maintain notes in Obsidian during development, export relevant notes as context at the start of each Claude Code session, update notes after each session with decisions made.
- The developer completed a weekend open-source project in roughly 12 hours of actual work, citing persistent context as the key factor in maintaining coherence across sessions.
- The approach works best for projects with many interdependent design decisions — for simple scripts or one-off tasks, the overhead isn't worth it.
Evidence
- The Reddit post included the actual Obsidian vault structure used, with example notes showing how architecture decisions were documented.
- Commenters noted this is essentially a more structured version of maintaining a CLAUDE.md file, with Obsidian's linking features adding value for complex projects.
- Several developers shared that they'd tried similar approaches with different note-taking tools (Notion, Roam) with similar results.
How to Apply
- Create an Obsidian vault for your project with notes for: architecture overview, key decisions (and why they were made), current state, and next steps.
- At the start of each Claude Code session, export the relevant notes to a context file and load it. The /memory command or CLAUDE.md can hold a pointer to the full vault.
- After each session, update your Obsidian notes with decisions made and new context. This investment pays off as the project grows.
- Use Obsidian's linking features to create a decision log — link related decisions together so you can feed Claude Code a coherent narrative of the project's evolution.
Code Example
# CLAUDE.md Template Example
## Project Overview
- Stack: Next.js 14, TypeScript, Drizzle, Turso
- Deployment: Vercel
## Coding Rules
- Components are always functional
- API routes go under /app/api/
## Memory Files
- Detailed context: ./obsidian-vault/context.md
- Work logs: ./obsidian-vault/logs/Terminology
Related Papers
Show HN: ctx – Search the coding agent history already on your machine
Claude Code, Cursor, Codex 등 코딩 에이전트가 이전 세션의 논의·결정·실패 시도를 잊지 않도록 SQLite로 인덱싱해 재사용할 수 있게 해주는 오픈소스 CLI 도구다.
Micro-Agent: Beat Frontier Models with Collaboration Inside Model API
vLLM 팀이 단일 모델 API 호출 뒤에서 여러 모델이 협업하는 'Micro-Agent' 개념을 공개했습니다. 별도의 에이전트 코드 없이 라우터 레이어에서 모델 조합을 실행해 GPT-4급 결과를 더 저렴하게 낼 수 있다는 아이디어입니다.
Ornith-1.0: self-improving open-source models for agentic coding
Gemma 4와 Qwen 3.5를 기반으로 파인튜닝한 코딩 특화 오픈소스 모델로, RL(강화학습)을 통해 스캐폴드(에이전트 실행 구조)까지 함께 최적화하는 방식을 주장하지만, 커뮤니티에서는 벤치마크 과최적화에 불과하다는 의심을 받고 있다.
Entity Binding Failures in Tool-Augmented Agents
AI 에이전트가 올바른 도구를 선택해도 잘못된 대상에 실행하는 'Entity Binding 실패' 문제를 정의하고, 이를 막는 실행 정책을 평가한 논문.
Herdr: Agent multiplexer that lives in your terminal
여러 AI 코딩 에이전트(Claude, Codex 등)를 하나의 터미널에서 동시에 실행·관리할 수 있는 Rust 기반 오픈소스 툴로, tmux처럼 세션이 유지되고 SSH로 원격 접속도 가능해 멀티 에이전트 워크플로우를 크게 단순화해준다.
Ornith-1.0: Self-scaffolding LLMs for agentic coding
모델이 문제 풀이 전략(scaffold)을 직접 생성하고 개선하는 자기강화 학습 프레임워크를 적용한 오픈소스 코딩 특화 LLM으로, 9B 소형 모델부터 397B 대형 모델까지 라인업을 갖추고 SWE-Bench 등 주요 벤치마크에서 Claude Opus 4.7을 능가하는 성능을 보여줬다.