Atoms

Get stuff out of your head into Obsidian — then have it filed, linked, and gently brought back so you can expand on it later.

The loop is simple:

1. Dump — capture a thought instantly (phone shortcut or a bullet in Daily Notes). No filing UI, no folders, no “where does this go?”
2. File — Atoms classifies past captures into flat notes under Atoms/ (title, tags, reason-bearing links). Your original words stay verbatim as the body.
3. Recall — home resurfaces filed notes (For you / mind-change / library) so you’re not stuck in a guilt task list. Open any atom in Obsidian and keep writing.

It’s a second brain inside your vault, not a separate app and not a CRM. Person hubs you already keep get real links and backlinks.

Paid services notice. Atoms needs a paid AI service to file anything. Pick one: bring your own Anthropic API key and Anthropic bills you directly for your usage, or subscribe to Atoms Plus (hosted, no key to set up, and the only way to ask from Claude or ChatGPT) from Settings inside the plugin. Pricing and a free trial are at tryatoms.app. The plugin code itself is MIT and free.

Plugin id: atoms · Version: see manifest.json · Requires: Obsidian ≥ 1.11.4, core Daily Notes, and either an Anthropic API key or Atoms Plus

Coding agents: start at AGENTS.md (claim rules + constitution). Humans do not need to memorize process — agents must.

Privacy & cost

• Each classify run sends vault note titles, tags, person-hub titles, and the capture text to the Anthropic API over TLS.
• Filing costs money either way. With your own key (stored in SecretStorage, never data.json) Anthropic bills you for the usage. With Atoms Plus you pay a monthly or yearly subscription instead, and requests go through the Atoms service. The plugin code is free (MIT); the AI behind it is not.
• The model never rewrites your hand-authored daily bullets. It creates flat atom files, appends markers, and (only when you choose Update notes) refreshes titles/links/tags on existing linker atoms — never the capture body.
• On Process title collision, existing atom files are not overwritten (protect-existing).
• Auto-run (device-local, default off) requires a one-time egress acknowledgment.

What it does

Non-negotiables

• Body of every atom = capture text verbatim
• Never move files or invent folders
• Auto-run never processes today’s daily (manual “Preview/Process today” exists for testing)
• API key in SecretStorage (or device-local fallback), never in data.json
• Write types: new atom files · append-only markers · user-initiated Update notes (model surfaces only)
• Second brain, not a task app — no due-date queue

Install

Community plugins (once listed)

1. Settings → Community plugins → turn on community plugins if needed.
2. Browse → search Atoms → Install → Enable.
3. Continue with First-run setup.

Beta / phone + desktop (BRAT — preferred)

1. Install BRAT.
2. BRAT → Add beta plugin → taihartman/obsidian-atoms.
3. Enable Atoms. After each GitHub Release, use BRAT Check for updates (desktop and phone vaults that use the same install path).

Manual (GitHub Release)

1. Download main.js, manifest.json, and styles.css from the latest Release.
2. Put them in <Vault>/.obsidian/plugins/atoms/.
3. Settings → Community plugins → refresh → enable Atoms.

Optional integrity check (after a CI-built release): download SHA256SUMS.txt from the same release, then:

shasum -a 256 -c SHA256SUMS.txt
gh attestation verify main.js -R taihartman/obsidian-atoms

First-run setup

1. Settings → Atoms → set your Anthropic API key (SecretStorage).
2. Confirm core Daily Notes is enabled.
3. Settings → Capture → install the iOS shortcut (or use the default iCloud link).
4. Capture bullets in daily notes, then use Atoms home → Preview → Process on past days (or the “including today” commands only for testing).

How to use (walkthrough)

Empty vault → dump into Daily → file into a linked library → open notes in Obsidian whenever you want to expand them. Screenshots are phone-frame product UI with synthetic dogfood (not personal notes).

1. First open — empty home

Open Atoms from the ribbon (library icon) or command palette → Open home. With no filed atoms yet, you get a setup card: write one bullet today, open today’s daily, install the capture shortcut.

2. Capture as daily bullets

Get it out of your head: top-level bullets in a past daily note (or today’s note if you only want to test later with “including today”). Phone shortcut or desktop typing both work.

3. Waiting to file

When past days have unmarked bullets, home shows a waiting card (and a queue peek). Today’s daily is never auto-processed. Add an API key if prompted, then Preview / Process (or enable automatic filing after the privacy ack).

4. Library after filing

Filed claims land as flat notes under Atoms/. Home lists them with optional person / work chips. Tap a row to open the atom in Obsidian and keep writing.

5. An atom note

Each atom keeps your capture text verbatim, plus frontmatter (created, source, tags, generated-by, quality stamps) and reason-bearing links the model proposed. Expand the note like any other Obsidian file.

6. Person hubs

Link to a person note you already keep (e.g. People/Jordan). Backlinks surface preferences and related atoms without a separate CRM.

7. Settings

Settings → Atoms: API key (SecretStorage), capture shortcut URL, model, atom folder, vocabulary. Version is shown at the top of the tab.

After you’re set up

• For you on home gently resurfaces filed atoms (calendar day, connections, quiet spacing) and mind-change pairs when you revised yourself — stream, not a review queue.
• Update notes (home strip or command) refreshes older atoms to current filing quality when the pipeline improves; original capture text still never changes.

Capture (phone)

1. Install the Atoms Capture shortcut from Settings → Capture (or Atoms home → Install).
2. Run it (or share text to it) to append a stamped line to the inbox note Atoms System/Inbox.md — the plugin creates that note and its Atoms Inbox bookmark for you.
3. When Obsidian next opens (or via the Drain inbox command), each line files into the daily for its stamp date, creating that daily if missing.
4. Preview / Process past days from Atoms home as usual.

Uses Obsidian's Capture to Bookmark, which appends with the app force-quit — so a capture on a day with no daily still survives. See docs/capture-shortcut.md.

Development

npm install
npm run dev          # watch-build main.js
npm test
npm run build
./scripts/install-to-vault.sh   # copy build into the throwaway vault
node scripts/seed-demo-vault.mjs           # synthetic README dogfood (full library)
node scripts/seed-demo-vault.mjs --empty   # first-day empty
node scripts/seed-demo-vault.mjs --waiting # past captures pending

Throwaway vault: test_vault/test vault/. Prefer that over a personal vault until dry-run looks right.

README screenshots use docs/media/demo-vault/ with fictional sample notes only (seed-demo-vault.mjs). Do not seed personal vault content into that folder.

Useful command palette entries

• Open home
• Dry-run: preview classifications / including today (test)
• Process unprocessed captures / including today (test)
• Update notes (refresh older atoms to current quality)
• Test connection
• Backfill: estimate cost & confirm batch

Docs

Repo

taihartman/obsidian-atoms

Releases ship main.js, manifest.json, and styles.css (plus SHA256SUMS.txt) for manual install and for the Community directory once listed. Assets are built in GitHub Actions on version tags with artifact attestations.

Cut a release (maintainers): bump manifest.json + package.json (+ versions.json via npm version / version-bump.mjs) on master, then:

git tag 0.6.x
git push origin 0.6.x

The Release workflow builds, attests, and attaches assets. Do not upload laptop-built main.js for production tags.

(Previously obsidian-ai-linker; renamed with the product.)

License

MIT — see LICENSE.