What problem does it solve?
Coding agents lose all session context, pending TODOs, and project architecture knowledge when a session ends, forcing you to re-explain past work, design decisions, and component relationships every time you start a new session.
Core Features & Use Cases
- Automatic session orientation: Reads pending TODOs and project overviews at session start without being asked, so the agent immediately understands current work priorities.
- Graph-based vault navigation: Uses the Obsidian CLI to look up component dependencies, architecture decisions, domain knowledge, and related notes on demand, minimizing context token usage.
- Bidirectional relationship management: Maps dependencies, extensions, and implementation relationships between code components with BFS tree walking for full dependency visibility.
- Session and project management: Tools to write session summaries, manage TODOs, scaffold new projects, and hydrate the vault with project metadata from existing repository documentation.
Use case: For a multi-session software project, the agent automatically picks up where you left off, remembers past architecture decisions, and logs new discoveries to the vault for future reference.
Quick Start
Use the obs-memory skill to initialize your Obsidian memory vault and enable persistent cross-session context for your coding agent.