Tagatha keeps a note's inline body tags reflected in its YAML tags property.
It adds missing body tags to frontmatter automatically and can optionally keep
tag removals synchronized in both directions.
For example, typing:
Consider billing options for client work #financial #client/billingadds the missing tags to the note's frontmatter:
---
tags:
- financial
- client/billing
---- Preserves a note's existing frontmatter tags.
- Case-insensitively avoids duplicate tags.
- Supports nested tags such as
#client/billing. - Is append-only by default. Removing an inline tag does not remove it from frontmatter (or vice versa) unless Synchronize tag removals is enabled in Tagatha's settings.
- With Synchronize tag removals enabled, removing a tag from either inline text or frontmatter removes every matching tag from the other location in that note.
- Compares tags case-insensitively and accepts a leading
#in frontmatter values without creating duplicates. - Runs locally and has no network access or telemetry.
Important: Tagatha automatically edits a note's frontmatter. When Synchronize tag removals is enabled, it can also remove matching inline tags. Back up your vault or try the plugin in a test vault before enabling two-way removal synchronization.
This option is off by default, preserving Tagatha's original append-only behavior.
When enabled, Tagatha remembers which tags each note has in inline text and frontmatter. If a tag that existed in both places is removed from either one, Tagatha removes it from the other. This prevents ambiguity when the two forms were already different: an existing frontmatter-only tag is not treated as an inline-tag deletion.
You can change the option at Settings → Community plugins → Tagatha. Turning it on records fresh snapshots; turning it off clears those snapshots and returns to append-only synchronization.
Requires Obsidian 1.13.0 or later. Tagatha supports desktop and mobile.
After Tagatha is approved, open Settings → Community plugins, select Browse, search for Tagatha, then install and enable it.
Download main.js and manifest.json from the
latest release, then place
both files in a vault folder named .obsidian/plugins/tagatha. Enable
Tagatha under Settings → Community plugins.
npm install
npm test
npm run buildThe production build creates main.js. Install it into an existing vault with
Python 3:
npm run install:vault -- --vault /path/to/vault --dry-run
npm run install:vault -- --vault /path/to/vault
# When Obsidian is running and this reload is authorized:
npm run install:vault -- --vault /path/to/vault --reloadThe installer backs up existing main.js and manifest.json to a printed
temporary directory, copies the build, and verifies both files. It preserves
data.json and does not enable the plugin. --reload uses Obsidian CLI to reload
Tagatha and display captured errors; use it with Obsidian already running. Build
and test the source before installing; the installer does not repeat those checks.
For a focused bug fix, run the existing tests and build once, then check the reported failure and intended behavior in one runtime scenario. Broaden runtime validation when the change affects data safety, other platforms, or a release.
Run npm version <version> --no-git-tag-version, update manifest.json and
versions.json to match, then push a tag with that exact version, such as
0.1.0. GitHub Actions validates all four version files, runs the tests, builds
the plugin, and attaches the runtime files to a GitHub release.