Source: raw/Every_Way_To_Set_Up_A_Claude_Second_Brain_Explained.md, raw/Stop_Using_Obsidian_for_Your_Second_Brain_Use_This_Instead.md

Creator: Ben AI · Platform: YouTube

Repo (verified 2026-10-28): naveedharri/baalda · Stars: 249 · License: Apache-2.0 · Site: baalda.com

Two Ben AI videos on the same question: where should a second brain live when more than one person uses it? In June he compared four options (a Claude skill, a synced storage folder such as Google Drive, a SaaS tool such as Notion, and Obsidian with the Relay sync plugin) and recommended Obsidian + Relay. In late August he launched his own open-source app, Baalda, built to fix what Obsidian lacks for teams: sharing, per-file permissions, backups and an MCP endpoint. The deciding variable in both videos is whether Claude reads the files locally or through a connector.

Key Takeaways

  • Local files beat connectors on efficiency. Ben says reading through an MCP or connector is “a little bit more token heavy”, “slightly less accurate” and “slightly slower”, but still gives “around 90% of the benefits”.
  • A synced storage folder is still local. Google Drive, OneDrive, Dropbox or iCloud desktop apps put the cloud folder on disk, so Claude reads it like any folder. The cost is sync delay and weak per-file permissions.
  • A skill is the fastest 80/20. Put the 6 or 7 core context files in one skill whose SKILL.md is a routing table. Share it as an organization skill on a Team plan. Updates flow one way only, from the admin.
  • Notion-style tools need a skill as the map. There is no folder, so no CLAUDE.md; a skill tells Claude where each kind of information lives in Notion and where to save.
  • Obsidian + Relay was the June recommendation, with Ben’s own permissions fork on top. Relay alone has no permissions.
  • Baalda is the August recommendation. Same local folder and graph view as Obsidian, plus email invites, real-time sync, per-folder and per-file permissions, daily backups with version history, and a built-in MCP endpoint for routines.

The options compared

OptionHow Claude reads itTeam syncPermissionsBen’s verdict
Second-brain skillSkill loads only the files its SKILL.md routes toOrganization skill on Team plan; admin-only updatesAdmin controls the single copyBest quick start; “more of a static second brain” with a size ceiling
Synced storage folder (Drive, OneDrive, Dropbox, iCloud)Local folder via the desktop sync appYes, with a delay of “sometimes a couple of minutes”; simultaneous edits can conflictHard to set per documentEasy if your files already live there
SaaS tool (Notion, ClickUp, Monday)Connector or MCP only, plus a skill as the mapNativeNative (Notion has read-only built in)About 90% of the benefit; fine if the team already works there
Obsidian + RelayLocal folderReal time via the Relay community plugin (free for up to three people, per Ben)None in Relay; Ben’s fork adds themJune pick for “the full most efficient setup”
BaaldaLocal folder; MCP endpoint for cloud agentsReal time; invite by email plus a join codeShared, read-only or private per folder, file or memberAugust pick; “free and open source”

Option details

Skill as second brain

  • Ben’s example is a “Ben AI OS” skill holding an about-me doc, voice guidelines, brand, ICP, customer pain points and his YouTube transcripts. Asked to help ideate a video, it read four of those files.
  • Progressive disclosure keeps it cheap: only the files the task needs are loaded (see Skills vs Projects).
  • Limits: no two-way sync, a cap on how much context fits, and no team memory of what people did in chats.

Synced storage folder

  • Build the brain locally first (folders, context files, CLAUDE.md), then move it into Drive and install the Drive desktop app on each machine.
  • Point Claude at the local copy of the Drive folder, not the Drive connector.

SaaS tool

  • Build the folder structure as a Notion template; Ben sells one in his paid community.
  • Each team member needs the Notion connector plus the “Notion OS” skill that routes Claude around the workspace.

Obsidian + Relay

  • Install Relay from Settings → Community plugins → Browse; everyone connects to the same Relay server.
  • Downsides Ben lists: every member must install and learn Obsidian, existing Drive or Notion content has to be moved, and Relay has no permissions. Full walkthrough with his fork: Ben’s Five-Skill AIOS Setup.

Baalda

Ben’s list of Obsidian gaps for a team brain: no team sync, no permissions, no version history or backups, and no way to expose the vault as an MCP so routines can update it. His August view of the workarounds (GitHub, Drive, Dropbox, iCloud, Notion, Relay): “clunky workarounds instead of real solutions”.

What the app does, per the demo and the repo README:

  • Local-first desktop app. Every note is a plain .md file on disk; Tauri v2 app for macOS, Windows and Linux (README). Local agents like Claude Code edit the files directly.
  • Team sharing. Vault settings → Members → invite by email as admin or member. The invitee downloads the app, logs in, enters a code and the full brain installs locally. Live presence shows who is editing.
  • Permissions. Vault settings → Access: shared, read-only or private per folder, subfolder or file, and per member. The README says MCP access goes “through the same ACL that governs people”.
  • Backups and history. Daily automatic backups, manual backups, owner can revert the vault; per-file version history with who changed what.
  • MCP connector. Vault settings → MCP → copy the endpoint URL; in Claude add a custom connector, log in, pick the vault. This is what lets a Claude Code routine update the brain with the laptop closed.
  • Self-hosting. Default sync goes through Baalda’s managed server. The repo has a “Deploy on Railway” button and a Docker Compose bundle (Tauri + Node + Postgres); point the app at your own server URL. Ben pitches this for GDPR needs.
  • Setup. Download from baalda.com; onboarding offers create vault, open existing folder, or join a team. Turn on sync under Vault settings → General.

Try It

  1. Under five people, not technical: build a second-brain skill with your 6 or 7 core files and a routing table in SKILL.md; add it to organization skills.
  2. Files already in Google Drive: move the brain into a Drive folder, install Drive for desktop, and point Claude at the local path. Accept occasional conflicts.
  3. Team lives in Notion: keep the brain there, write a Notion routing skill, and give everyone the Notion connector.
  4. You want local speed plus team sync and permissions: open your existing folder in Baalda (free), turn on sync, set the strategy and root routing files to read-only, invite one teammate.
  5. You need routines to update the brain: copy Baalda’s MCP URL into a custom connector, then create a routine that reads your meeting recorder and writes to the brain through that connector.

Open Questions

  • App name. Auto-captions render it as “Balder”, “Baldur”, “Balda” and “BA”. The repo and site confirm Baalda (baalda.com). Ben’s description of it as built by “me and my team” while the repo sits under naveedharri is unexplained; the owner may be a team member.
  • Pricing of the hosted version. The README says the self-hosted stack is free and offers a managed service; Ben calls the app free. Paid tiers, if any, were not checked.
  • Relay’s free limit of three people and Relay’s planned permissions feature are Ben’s statements (April 2026); not verified against Relay’s current plans.
  • Ben’s “around 90% of the benefits” via connectors is his estimate, not a measurement.