Skip to documentation content
DocumentationVersion 2
Browse documentation
DocumentationReference

What changes in V2

Compare the V2 workflow and architecture with V1 without assuming an in-place upgrade.

On this page

This page describes the V2 changes covered by these guides. It is a version overview, not a dated release announcement or a record of download availability.

One dedicated plugin

V2 provides native tasks, metadata indexing, commands, views, templates, widgets, icons, reminders, and updates. Its core workflows do not require the V1 chain of community plugins.

Native obsibrain blocks replace the supported legacy view workflows. Existing custom Dataview queries and Templater scripts need review; they do not run as native V2 templates or widgets.

User-owned structure

Entity identity comes from the note’s type property. Projects, goals, and other typed notes can live in your chosen folders.

Creation commands read editable templates under templates/obsibrain/. Normal provisioning creates missing defaults and preserves existing files. The root dashboard remains editable Markdown.

Each review cycle has a settings toggle. The widget library offers contextual views and an Add action for mobile use.

Clearer workflow boundaries

Projects derive completion from counted internal and linked tasks. Goals retain explicit completion and separate task and project progress.

Completed-task cleanup requires a manual command, preview, and confirmation. Reminders operate while Obsidian is open. Automatic updates include a reload warning with Later.

Optional desktop AI Alpha provides read-only vault chat through Pi. It requires consent before excerpts reach the chosen provider.

A separate V1 transition

V2 uses the plugin ID obsibrain; V1 uses obsibrain-plugin. V2 stops while V1 is enabled in the same vault.

The desktop migration wizard analyzes supported V1 vaults and creates recognized target content. It preserves the source and existing target files, with manual review for warnings and custom workflows.

Read installation for setup and updates for the updater’s behavior.

V1 releases