Skip to content

Folder First AI Shared Vaults 1.0.0

Latest
Latest

Choose a tag to compare

View all tags
@micahhorner micahhorner released this 03 Oct 09:17
· 3 commits to main since this release
1.0.0
8be8dc6

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.

Assets 5
Loading