v0.23.0 — Obsidian vaults & Notion pages as living sources
Highlights
- Obsidian vaults are living sources. Add a folder that contains
.obsidian/and Alchemy recognizes it as a vault — a distinct icon, an "Obsidian vault" label, and a vault map. Your notes'[[wikilinks]]render as clickable hops between notes (resolved by Obsidian's shortest-path rule), YAML frontmatter is kept as provenance instead of polluting retrieval, and atags:list feeds the search context. Folders you added before this update upgrade themselves to vaults on their next sync — no re-adding. - Notion pages are living sources. Create an internal integration, share pages with it, and paste a
notion.soURL: the page and its child-page tree import as one source, re-syncing whenlast_edited_timemoves — only the pages you actually changed re-embed. Settings → Sources has a Notion token field that validates against your workspace as you type ("Connected to …") with a one-click link to create the integration. - Notion databases come in as tables. A database inside a page renders as a markdown table of its rows — titles, links, select/status, dates, people, and more — so "what's in this list" questions answer straight from the source.
Fixes
- Long Settings tabs (Models, Appearance, Agents) scroll again — a height regression let them grow past the modal instead of scrolling within it.
- The provider add/edit wizard has a consistent "‹ Back" to the provider list from every step.
Notes
- Notion access uses an internal integration token you create at notion.so/my-integrations; it's stored locally and sent only to Notion. Sharing a page with the integration is the permission model — Alchemy sees only what you share.
- Vaults and Notion pages ride the same machinery as folders and git repos: the same auto-sync cadence (Settings → Sources), the same reader tree, the same promote/demote and grep retrieval. Nothing new to configure.
- Design details in
docs/RFC-obsidian-notion.md.
Full Changelog: v0.22.0...v0.23.0