Persist Claude Code session context, decisions, and troubleshooting history into an Obsidian vault with auto-categorization, then search that vault by keyword or type to recall past project knowledge during future sessions. Automate vault structure audits and refactoring via Socratic interviews.
Enable automatic session save on exit (Registers SessionEnd hook)
Search and recall past documents, decisions, and troubleshooting from the vault
Interactive vault refactoring wizard to reorganize an existing Obsidian vault
과거 Claude Code / Codex 세션 기록을 vault에 구조화된 문서로 복원
Save current session context and work summary to the vault
Expert at validating file and directory migration plans, ensuring no data loss or overwrite conflicts occur during vault refactoring
Expert at conducting Socratic interviews to clarify vault setup requirements — asks focused questions, never builds
Expert at reading Claude Code session transcripts and extracting structured summaries with decisions, errors, and action items
Expert at designing Obsidian vault structures for team knowledge management, categorizing information, and organizing document hierarchies
Expert at analyzing existing Obsidian vault structures and conducting Socratic interviews to identify pain points and refactoring needs
Manage the Obsidian vault structure, organize documents, add new files, and maintain the team's knowledge base. Use this skill when the user wants to organize, categorize, or restructure their vault contents, or when adding new documents that need proper placement. Triggers: vault, 볼트, 문서 정리, 분류, organize vault, add document, 정리해, vault structure, vault 관리, 볼트 구조, 카테고리, 폴더 정리, 문서 추가, organize, categorize, knowledge base, 지식 베이스, 노트 정리
Automatically recall relevant past context from the Obsidian vault when the user asks about past decisions, previous work, how something was done before, troubleshooting history, or project knowledge. This skill searches the team's knowledge base to provide historical context. Triggers: 회상, 기억나, 이전에, 어떻게 했지, recall, remember, how did we, what did we decide, past decision, 이슈 해결, 작업 기록, 이전 작업, 과거, 히스토리, 히스토리 확인, 찾아줘, 검색, find, search vault, what was the decision on, how was X implemented
Save current session context and work summary to the Obsidian vault when the user asks to record or save their work. Automatically generates a structured markdown document capturing what was discussed, decisions made, and next steps. Triggers: 기록해, 저장해, save session, 세션 저장, 작업 기록, 이 작업 기록, save this, record this, 기록, 저장, 로그, log, document this, 회의록 작성, 정리해줘
Uses power tools
Uses Bash, Write, or Edit tools
Runs pre-commands
Contains inline bash commands via ! syntax
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
◯ ─────────── ◯
O H - M Y - O B S I D I A N
◯ ─────────── ◯
Stop forgetting. Start remembering.
Give your AI coding agents a permanent, evolving second brain.
Quick Start · Why · How It Works · Commands · The Agents
Oh-my-obsidian transforms Claude Code into an agent with infinite memory.
AI coding agents are brilliant but amnesiac. Oh-my-obsidian bridges this gap by integrating an Obsidian vault directly into your Claude Code workflow. Through Socratic interviews, automated refactoring, and real-time Git sync, your AI learns your project's context, records its decisions, and recalls them perfectly across sessions.
Most AI coding agents start every session with a blank slate.
| Problem | What Happens | Oh-My-Obsidian Fix |
|---|---|---|
| Amnesia | AI forgets why a decision was made last week | session-save records architectural decisions into Markdown |
| Lost Context | You paste the same context over and over | recall automatically searches the vault for relevant past work |
| Messy Docs | Documentation rots and becomes disorganized | refactor safely reorganizes the vault as the project evolves |
| Setup Friction | Hard to bootstrap a good folder structure | Socratic setup interviews you to generate a tailored vault |
# 1. Add our custom marketplace
/plugin marketplace add https://github.com/hongdangmoo49/oh-my-obsidian
# 2. Install the plugin
/plugin install oh-my-obsidian@omob
Install via Official Marketplace — (Pending Approval) If installed from the official Claude registry:
/plugin install oh-my-obsidian
(For local development: claude --plugin-dir /path/to/oh-my-obsidian)
Initialize — Run the interactive Socratic setup wizard:
> /oh-my-obsidian:setup
Codex reads the repository marketplace from:
.agents/plugins/marketplace.json
Add the marketplace from GitHub:
codex plugin marketplace add hongdangmoo49/oh-my-obsidian
Then open Codex and install oh-my-obsidian from the plugin directory:
/plugins
Then ask Codex:
Set up an Obsidian vault for this project.
After setup, you can continue with Codex using natural-language prompts or an explicit skill name such as:
What did we decide last time about the vault layout?
Save this session to the Obsidian vault.
Show me the vault health check.
Add a note to the vault for today's API decisions.
$oh-my-obsidian-recall Find our prior vault-layout decision.
The plugin will:
vault-architect agent.safe, manual, or team-sync) after separate approvals.Codex support is shipped from a separate plugin root:
plugins/oh-my-obsidian/
Use the Codex-native marketplace file:
.agents/plugins/marketplace.json
When users add hongdangmoo49/oh-my-obsidian as a Codex marketplace source,
Codex reads this marketplace and exposes the bundled oh-my-obsidian plugin.
Do not reuse .claude-plugin/marketplace.json for Codex.
Typical Codex start flow:
codex plugin marketplace add hongdangmoo49/oh-my-obsidiancodex, then open /plugins and install oh-my-obsidianSet up an Obsidian vault for this project.The Codex plugin keeps the same product shape: guided setup, recall, session-save, vault management, and official Codex hooks for project-local memory context. In Codex, these flows are typically used through natural-language prompts or explicit skill invocation rather than Claude-style slash commands.
npx claudepluginhub hongdangmoo49/oh-my-obsidian --plugin oh-my-obsidianPersistent Obsidian-based memory for coding agents. Automatically orients from a knowledge vault at session start, navigates project architecture via graph traversal, and writes discoveries back to the vault.
Create and edit Obsidian vault files including Markdown, Bases, and Canvas. Use when working with .md, .base, or .canvas files in an Obsidian vault.
Automatic Claude Code -> Obsidian second brain: zero-config session capture, hybrid search, autonomous recall, daily/lessons/preferences.
A self-developing knowledge management system for Claude Code. Bridges AI memory to an Obsidian vault with feature-organized spine notes, auto-capture skills, and color-coded graph visualization.
Knowledge management for Obsidian vaults and structured markdown repositories
Manage an Obsidian vault as your development knowledge base and automatic work journal. Auto-captures commits, tasks, and Claude Code components with structured frontmatter.