pumice 0.2.0 (link)
I made an Emacs package for Obsidian vaults! I use and love Obsidian but I found it was using a lot of RAM at times, so I went looking for an alternative. I still wanted my Obsidian notes to be accessible and work on my phone without having to migrate them to a new tool, so I made an Emacs package that works on existing Obsidian vaults. Markdown and wikilinks work, and it reads each vault's .obsidian settings to find out where daily notes, templates and new notes should go. It doesn't add anything of its own to the vault, so the Obsidian vault keeps working on other devices with the exact same files.
It's named after another volcanic rock that's like obsidian but full of air pockets, so it's lighter.
This is what it looks like:

Installation instructions are in the readme.
What it does#
With pumice you can jump to a note by name or alias (or start a new one if nothing matches), follow [[Note]], [[Note#Heading]], [[Note|shown text]] and ![[embeds]], and complete note names after [[, headings after [[Note#, and tags after #. Links resolve the same way Obsidian resolves them, including when two notes share a name, so a link means the same thing in both apps.
There's a backlinks panel that follows whatever note you're in. It lists the lines that link to the note, the lines that mention it without linking (you can turn those into links right from the panel), and the note's own outgoing links. There's a folder tree in a side window, too. Daily notes use the vault's own folder, date format and template, and templates understand Obsidian's {{title}}, {{date}} and {{time}} variables. Renaming or moving a note rewrites every link to it, and you can pull a region out into a note of its own.
The command line, and agents#
Pumice comes with a pumice command that runs the same index in a batch Emacs, so scripts and coding agents can ask the same questions without Emacs or Obsidian running:
pumice backlinks "Weekly Review"
pumice list --tag project --where status=active --show next_action
pumice log "Sent the invoice" # a timestamped line in today's daily note
pumice rename "Old name" "New name" # rewrites every link to the note
This is how my own agents work with my notes now. Obsidian's own command line starts the Obsidian app, and the mv and rm agents use by default leave links dangling, whereas pumice rename and pumice trash keep them working. The repo includes a skill for Claude Code in contrib/skills/pumice, and the README has a short snippet to paste into AGENTS.md for other agents.
What's new in 0.2.0#
The very first release went out yesterday but this one aims to smooth out some of the rough edges getting it set up.
- With no vault configured, pumice tells you how to name one instead of failing with a raw error.
- A vault folder that doesn't exist is reported as missing, and pumice never creates it for you, since that would be a change you didn't ask for and can't undo. A missing folder also no longer sticks around as the default vault.
- A mistyped
--vaultpath is reported as a missing folder. pumice vaultsmarks the vault a command run from where you are would use, and lists a vault only once however its path is spelled (through a symlink, say).- An empty template folder says it's empty, instead of offering every note in the vault as a template.
- Setting
PUMICE_EMACSto something that can't be run fails with a clear message. - The README now walks through starting a vault without Obsidian, installing the command line, and setting it up for coding agents.
Known limitations#
Pumice doesn't render embeds or Markdown inline, draw a graph, run Obsidian plugins, or sync anything. Dataview queries, canvases and .base files show up as files you can link to, not the way Obsidian draws them. Frontmatter is read as the flat properties Obsidian writes, not as arbitrary YAML.
It's early days, so if you try it and run into anything, please open an issue on the repo. Thanks for reading!