Prepare Node.js, the destination path, and your Obsidian decision before installation.
Last reviewed:
About this guide
This guide was prepared with AI assistance using the project’s public documentation. It does not claim testing on every device or independent human review. Project publisher: AmirSina Zamanian.
Sources are listed at the end. Use the project repository to report an error or suggest a correction. Report an issue
⌕
Search runs on this device.
On this page
Overview
You need a compatible Node.js installation and a trusted local destination. Obsidian provides the full memory layer; without it, you can choose Dashboard-only, but full shared memory is unavailable. Setup time depends on whether Obsidian is installed and is only an estimate.
Check your runtime
You need Node.js 20 or newer. Run node --version and then npm --version to check your runtime. If a command is missing, fix the Node.js installation and executable path first; administrator privileges are not the default workaround.
Choose destinations and installation mode
Prepare a writable local destination and sources you are authorized to read. Use Obsidian for full memory; Dashboard-only has limitations. Back up existing data and compare the proposed destination with the location you intended.
When are you ready?
Continue when Node.js is compatible, the destination is known, and you have selected the tools and sources you need. Setup duration depends on existing installations and source count; no guaranteed or unmeasured duration is claimed.
Completion checklist
Before installation, confirm:
1. Node.js and npm commands run successfully.
2. You recognize the local destination and can write to it.
3. You own or are authorized to read the selected sources.
4. You have chosen Full or Dashboard-only mode.
5. Existing files are backed up.
What should you prepare?
Public version 0.10.0 requires Node.js 20 or newer and npm. Check node --version, npm --version, and git --version separately. Distinguish three destinations: the Vault, application data and configuration, and the project directory for adapters. Choose empty non-sensitive directories for the first experiment; do not use your home root or entire disk as a data source.
Do not guess price, subscription, or budget values. The tested wizard accepts [] for list inputs; that means no data was supplied, not zero cost. Distinguish missing usage sources from ready instruction files. Use the lab below to inspect the mechanism without real connections; actual analytics require a separately approved source.