Auto folder tags

approved

by gansxx

Automatically apply configured tags to new notes and supplement tags for files in the current folder. - This plugin has not been manually reviewed by Obsidian staff.

↓ 175 downloadsUpdated 2mo agoMIT
Install in ObsidianView on GitHub

Auto folder tags

Automatically apply configured tags to new notes and supplement tags for files in the current folder.

Features

  • Listen for newly created markdown files and inject configured frontmatter tags.
  • Apply the same configured tags to all markdown files in the current folder from the command palette.
  • Avoid duplicate tags when the note already contains some or all target tags.

Installation

Manual install

  1. Download manifest.json and main.js from the latest GitHub release.
  2. Create the folder .obsidian/plugins/auto-folder-tags/ inside your vault.
  3. Move the release files into that folder.
  4. Reload Obsidian and enable Auto folder tags in Settings -> Community plugins.

Community plugins

After the plugin is approved by the Obsidian team, it will be installable from the in-app community plugins browser.

Configuration

  1. Open Settings -> Community plugins -> Auto folder tags.
  2. Add one or more rules.
  3. Set each folder path relative to the vault root, for example Inbox or Projects/ClientA.
  4. Enter tags as comma-separated values, for example tag1, tag2.

The plugin uses the longest matching folder rule. A rule for Projects/ClientA overrides a broader rule for Projects.

Commands

  • Apply configured tags to files in the current folder
  • Open auto folder tags settings

Privacy and disclosures

  • The plugin works locally inside the vault.
  • It does not send note content, filenames, or telemetry to external services.
  • It does not require any cloud account or network access for normal operation.

Development

  1. Run npm install
  2. Run npm run check
  3. Run npm run dev while developing
  4. Run npm run build for a production bundle

Release and submission

  • The repository includes GitHub Actions for CI and release asset uploads under .github/workflows/.
  • The release workflow also generates GitHub artifact attestations for the uploaded release assets.
  • The submission helper files live in submission/.
  • Release tags must exactly match manifest.json version, for example 0.0.1.

Sandbox preview

The preview helper defaults to the Obsidian Sandbox vault under %APPDATA%.

node preview-in-sandbox.js --enable-plugin

Use a different vault only when needed:

node preview-in-sandbox.js --vault-path "D:\\My Vault"

For plugin developers

Search results and similarity scores are powered by semantic analysis of your plugin's README. If your plugin isn't appearing for searches you'd expect, try updating your README to clearly describe your plugin's purpose, features, and use cases.