Obsidian Stats logoObsidian Stats

Folder First AI Shared Vaults

by Folder First AI
5
4
3
2
1
Score: 41/100
Install Code

Description

Connect and safely refresh approved Company and Team shared vaults from GitHub in Obsidian.

Reviews

No reviews yet.

Stats

0
stars
2
downloads
0
forks
1
days
1
days
1
days
7
total PRs
4
open PRs
1
closed PRs
2
merged PRs
0
total issues
0
open issues
0
closed issues
18
commits

Latest Version

1.0.0
a day ago

Changelog

Folder First AI Shared Vaults 1.0.0

Folder First AI Shared Vaults keeps approved company and team guidance available inside a prepared Folder First AI Workspace.

Employees use two actions in Obsidian:

  1. Connect vaults downloads the Company and Team vaults their work GitHub account may access.
  2. Refresh all receives later approved updates.

The plugin places those Markdown files in their prepared Shared/ folders, where Claude Code, Codex and other folder-aware AI tools can use them alongside the employee’s own working context. It never manages the employee’s My Work/ folder.

Why this is useful

  • Leadership maintains one approved Company vault and separate Team vaults.
  • GitHub repository permissions control which shared vaults each employee may receive.
  • Employees do not type repository addresses or choose destination folders.
  • Shared context remains ordinary Markdown in normal folders, so the organization can inspect, back up and move it without a proprietary database.
  • If an employee accidentally edits a shared file, refresh stops safely. A confirmed Restore approved copy action can remove only the local shared-vault changes that the plugin knows how to repair.

Requirements

  • A prepared Folder First AI Workspace with Shared/VAULTS.yaml configured by the implementation specialist.
  • Obsidian desktop 1.13.7 or newer. Mobile is not supported.
  • System Git and Git Credential Manager.
  • A normal work GitHub account with read access to the configured Company and Team repositories on GitHub.com.

Security and privacy boundary

  • Receive-only: the plugin does not push, commit or edit the source repositories.
  • No Folder First AI server, analytics or telemetry.
  • No GitHub password or token is stored in the Obsidian vault.
  • Authentication is handled by Git Credential Manager and the operating system’s credential store.
  • Updates are deliberate. There is no background refresh in 1.0.0.
  • Unexpected local history, unsafe paths, symlinks, submodules and meaningful local edits fail safely instead of being overwritten.

Installation

Until the plugin is accepted into the Obsidian Community directory, an implementation specialist may install the exact reviewed release files into:

.obsidian/plugins/folder-first-ai-shared-vaults/

Install all three assets from this release:

  • main.js
  • manifest.json
  • styles.css

Then enable Folder First AI Shared Vaults under Settings → Community plugins. Client IT should approve Obsidian, Git, Git Credential Manager and the intended GitHub repositories before rollout.

Reviewed asset hashes

8006d4a94fa1aa7046fd71071450f4443f3b32c098fdb200e4a5e99f9bf1bcc8  main.js
9dce4e7d8c905ffd7f94b3068baf38f21e6d35c538311742936aec905aaa2e51  manifest.json
a3753440da683b79fd6c6f7d0475c38d663fe99f8a2c10fd0eceda02bc39ee2b  styles.css

Known limits

  • GitHub.com repositories only in 1.0.0.
  • Desktop Obsidian only.
  • Employees click Refresh all to check for updates.
  • The exact source and release assets passed hosted Windows checks. Earlier native Windows testing demonstrated the core connect and refresh path, but the final selected build was not repeated end to end on the physical Windows test laptop after that device became unavailable.
  • A shared vault is limited to 25,000 files, 220 UTF-8 bytes per repository path, 100 MiB per file and 1 GiB of directly versioned content.
  • Removing GitHub access stops future refreshes but deliberately keeps the last approved local copy. Offboarding and local-file removal remain an organization policy decision.
  • Community-directory acceptance and client-specific IT approval are separate from this GitHub release.

The source is available under the MIT License. See README.md, SECURITY.md, RECOVERY.md and THIRD-PARTY-NOTICES.md for implementation and support details.

See all version on GitHub

README file from

Github

Folder First AI Shared Vaults

Shared Vaults is a desktop-only Obsidian plugin that places an employee’s approved Company and Team GitHub repositories in prepared folders inside a Folder First AI Workspace.

Version 1.0.1 is the current public release. Install it from Obsidian’s Community Plugins directory or from the reviewed GitHub release.

What employees do

  1. Open the prepared Folder First AI Workspace in Obsidian.
  2. Open Shared Vaults.
  3. Select Connect vaults and complete GitHub’s browser sign-in if asked.
  4. Select Refresh all when they want to check for approved Company or Team updates.
  5. If an accidental local edit blocks one shared vault, preserve anything useful in My Work, then use that vault’s confirmed Restore approved copy action and select Refresh all again.

The implementation specialist prepares Shared/VAULTS.yaml. Employees do not enter repository URLs, branches or folder paths.

Requirements

  • Obsidian desktop on macOS or Windows. Mobile is not supported.
  • A recognized Folder First AI Workspace.
  • System Git and Git Credential Manager installed and configured by the employee, implementation specialist or IT team. On macOS, use GCM's official package/Homebrew installation or an already approved GitHub Desktop GCM configuration; on Windows, use the normal Git for Windows installation.
  • A GitHub account with access to every repository assigned in Shared/VAULTS.yaml.
  • Network and browser authentication access permitted by the organization.

The plugin does not install or update Git, Git Credential Manager, Obsidian, itself or any dependency.

Safety boundaries

Shared Vaults:

  • writes receiving copies only to Shared/Company and prepared Shared/Teams/<team> folders;
  • never reads or changes My Work during delivery operations;
  • never pushes, commits, force-resets a remote branch or resolves merge conflicts;
  • stores no GitHub password or token;
  • opens authentication only after the employee deliberately selects Connect vaults;
  • keeps existing local files when a refresh cannot reach GitHub or access is unavailable;
  • refuses local commits, divergent history, symlinks, submodules, incompatible paths and repository-controlled checkout-filter/LFS configuration;
  • refuses receiving repositories above 25,000 files, paths above 220 UTF-8 bytes, any single file above 100 MiB, or more than 1 GiB of directly versioned files;
  • collects no telemetry and has no Folder First AI server or account.

Restore approved copy is intentionally narrow. After confirmation, it removes uncommitted tracked and untracked non-ignored changes only inside one validated shared-vault receiving clone. It refuses local commits or divergent history. It does not update from GitHub; the employee selects Refresh all separately.

Closing the Shared Vaults view or disabling the plugin cancels the active Git command and its helper processes. A partial staging folder is never treated as a connected receiving copy.

Removing someone’s GitHub access prevents later authenticated checks but cannot erase files already downloaded to their computer. Client IT owns endpoint retention and offboarding.

Network and system access disclosure

The plugin invokes the computer’s system Git executable. Git connects to the https://github.com/<owner>/<repository> URLs prepared in Shared/VAULTS.yaml and uses the computer’s configured Git Credential Manager/browser flow. The plugin reads its current Obsidian vault and writes only the configured receiving paths plus its private runtime folder under Shared/.folder-first-ai-delivery.

Like all Obsidian Community plugins, it inherits Obsidian’s desktop permissions. Organizations should review the source and release hashes before approving it for sensitive workspaces.

Updates

Obsidian obtains compatible plugin updates from this repository’s GitHub releases. The plugin never updates itself. Managed organizations may pin a reviewed version through their normal software change process.

A plugin update changes plugin software only. It must preserve Shared/VAULTS.yaml, downloaded shared vaults, plugin state and My Work. Folder First AI Workspace file upgrades are separate release-specific changes.

Development

Development requires Node.js 22.6 or newer. Employees do not need Node.js.

npm ci
npm run lint
npm test
npm run build

The production build writes the Community-release asset main.js at the repository root. A valid release also attaches the matching root manifest.json and styles.css under a Git tag identical to the manifest version.

GitHub artifact attestations record the exact SHA-256 identities of the published release files. A downloaded file can be verified with GitHub CLI:

gh attestation verify --owner FolderFirstAI <filename>

Support and security

Use GitHub Issues for reproducible non-sensitive defects. Do not post credentials, private repository names, client content or logs containing private paths. Report a vulnerability through the repository’s private GitHub Security Advisory channel; see SECURITY.md.

Shared Vaults is licensed under the MIT License. Third-party components and licenses are listed in THIRD-PARTY-NOTICES.md.

Sponsors