Mind map editor

Edit your outline as a mind map, synced to Markdown. No new file format, no markup to add.

Usage

1. Open a Markdown file.
2. Press Ctrl+P (Cmd+P on macOS) and run Open mind map for the active file (or click the ribbon icon).
3. The map opens in a split and stays in sync while you type.

Features

• Automatic mind map - Headings and bullet lists become nodes, with the note title as the root; heading depth and list indentation define the hierarchy. Headings are bold pills with a color-tinted fill; list items are plain pills.
• Edit on the map - Rename, add, delete, drag & drop. Dropping on a node's middle makes it a child; dropping near a sibling's top/bottom edge inserts it there.
• Working checkboxes - Clicking toggles [ ] ⇄ [x] in the file.
• Collapse completed tasks - The ✓✓ header button folds checked tasks into one ✓ n done pill per parent. Click a pill to reveal just that parent (− hide done folds it back). Remembered across sessions.
• The editor always follows the selection - Selecting a node (by click or arrow keys) moves the Markdown editor's cursor to its line and briefly highlights it, without stealing focus from the map.
• Follow wikilinks - Clicking a [[wikilink]] switches map and editor to the linked note together.
• Branch colors - Each top-level branch gets a palette color by position and its subtree inherits it. Customize the palette in settings, one hex color per line.

Keyboard shortcuts

Active while the mind map pane is focused.

Back/forward use Obsidian's own Navigate back / forward command: Ctrl + Alt + ←/→ (Cmd + Option + ←/→ on macOS).

Toggle focus between mind map and Markdown editor can be bound to one in Settings → Hotkeys to jump between the two.

Settings

Settings → Mind map editor:

• Follow active file (default on)
• Hide completed tasks
• Split direction - Side by side / stacked; also updates itself when you rearrange the map pane.
• Branch colors - Custom palette, one hex color per line.

npm install
npm run dev    # watch build
npm run build  # type check + production build
npm run lint
npm test       # run the Vitest unit tests (npm run test:watch to watch)