obsidian-second-brain
Obsidian Second Brain stores agent knowledge and context in Markdown, while its Crew feature provides a shared job log for multiple agent hosts. Crew also works in a plain folder without Obsidian. This is useful when a team wants inspectable handoff records and accepted lessons before adopting a more elaborate memory service. We reviewed the Crew workflow at a fixed 0.20.0 source revision using Python 3.12.13. The local runtime uses the standard library; the broader research and vault features have separate requirements.
Ten checks exercised the actual command entry point with three filesystem resolvers redirected to temporary destinations. Setup reruns preserved unrelated rules and did not duplicate hooks. A job was consumed once by one session and remained independently readable by another session. An open lesson did not change recipient rules; explicit keep promoted it once, and an opposite final decision was rejected. Independent CLI processes retained all 24 concurrent local writes. Malformed hook JSON stopped setup without rewriting existing rules. No real agent configuration or existing vault was modified.
An important limit appeared with bounded unread reads: only the latest requested records were displayed, but older omitted history was also marked consumed. Use a digest or inspect the log for complete historical review. The human keep convention is not authenticated enforcement, and local concurrent writes do not establish distributed synchronization safety. We did not load generated hooks in a host, call a model, assess semantic retrieval or test automatic vault rewriting. Choose Crew for a narrow file-based handoff trial, then separately verify that the chosen host receives and uses its context.
Read the full review, verification scope and sources →Features
Why choose it
Trade-offs
Maintenance check
- Last commit
- 2026-11-10
- Commits, last 90 days
- 100+
- Releases, last 90 days
- 7
- Latest release
- v0.20.0 (2026-10-25)
- Open issues
- 7
- Recent issues with at least one comment
- 11/15
Oldest week on the left; the latest four weeks are orange. Source: GitHub commit activity.
Status rule: archived on GitHub = Archived; last commit within 90 days = Active; 91 to 365 days = Slowing; older = Stale. All figures come from the GitHub API on the date shown.
Most discussed open issues
- #171 Own a platform build: six of eight are open29 comments · 2026-07-26
- #337 [Feature] Add opt-in Parallel Search MCP to free research4 comments · 2026-10-11
- #163 i18n: add trigger phrases for a new language4 comments · 2026-07-26
- #398 [Feature] Crew: let decided lessons leave hook reads, and keep hook reads under the host's size limit2 comments · 2026-11-09
- #386 Search falls back to lexical without a word when the embedder is slow2 comments · 2026-11-04
Issue titles are quoted from GitHub. Open the link to check whether a problem still applies to the version you use.
Who it fits
- You want readable job handoffs in a plain local folder.
- You will review lessons and separately verify host-visible context.
- You need measured semantic-memory accuracy or automatic task coordination.
- You require distributed consistency or authenticated lesson approval.
Compatibility
Quick start
Use cases
Alternatives
Comments
No comments yet. Be the first!