explaingit

xheldon/vaultecho

Analysis updated 2026-05-18

0JavaScriptAudience · vibe coderComplexity · 3/5Setup · moderate

TLDR

An Obsidian-native gateway that turns structured input from automation tools like Coze or Shortcuts into Markdown notes, with semantic search and scheduled AI review.

Mindmap

mindmap
  root((VaultEcho))
    What it does
      Capture Gateway
      Writes to Vault
      Audit-safe Writes
    Tech stack
      Node.js API
      Vue Admin UI
      Docker Compose
    Features
      Semantic Recall
      Scheduled AI Review
      Daily Note Rules
    Use cases
      Shortcuts Capture
      Automation Routing
      Weekly Summaries
    Audience
      Obsidian Users
      Automation Builders

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Send captured text from an iPhone Shortcut or automation platform straight into an Obsidian vault as a Markdown note.

USE CASE 2

Search past notes by meaning rather than exact keywords using the built-in semantic index.

USE CASE 3

Get automatic weekly, monthly, or yearly AI-written summaries of your notes written back into the vault.

USE CASE 4

Run a lightweight note capture backend on a small VPS without a local AI model or database server.

What is it built with?

JavaScriptNode.jsDockerVueVite

How does it compare?

xheldon/vaultechoabhishek-akkal/finovaadan-shahid/ecommerce_website
Stars000
LanguageJavaScriptJavaScriptJavaScript
Setup difficultymoderateeasymoderate
Complexity3/51/53/5
Audiencevibe coderdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 30min

Requires a local vault already managed by Obsidian Headless Sync running separately, plus Docker Compose for the service itself.

In plain English

VaultEcho is a bridge between automation tools and a note vault managed by Obsidian. It captures input from things like Coze, n8n, or Apple Shortcuts, turns that input into structured data, and writes it as Markdown files into a local vault that Obsidian keeps in sync in the background. The project itself does not try to understand or transcribe what you send it. That work is left to Coze or another automation platform. VaultEcho's job is narrower: take the structured result and write it into the right place in the vault, safely and in a way you can audit later. Before running VaultEcho, you need a local vault folder that is already being kept in sync by Obsidian's headless sync feature, a separate process running in the background. VaultEcho reads and writes Markdown files in that folder, but it does not manage the syncing itself, log into Obsidian, or handle your Obsidian account. It is meant to run alongside a sync process that someone else is responsible for. Setup is done through Docker Compose, and once running, a web based admin panel lets you configure things like where notes go, daily note formatting rules, time zone handling, and file size limits. The admin interface protects itself with basic authentication so it is not left open by accident. Beyond simple capture, VaultEcho also builds a searchable index of your notes using an external embedding API, which turns text into a form a computer can compare for similarity. This lets it support semantic recall, meaning it can find notes related to a topic even if they do not share exact words. It can also run scheduled AI review tasks, such as weekly or monthly summaries, that read through recent notes and write a summary back into the vault on a schedule you define. The project is designed to run cheaply, on a small low powered server, without needing a local AI model or a dedicated database.

Copy-paste prompts

Prompt 1
Help me set up VaultEcho with Docker Compose to write into an Obsidian vault that's already synced with Obsidian Headless Sync.
Prompt 2
Show me how to send a POST request from an iPhone Shortcut to VaultEcho's API with a Bearer token in the API_TOKEN header.
Prompt 3
Explain how VaultEcho's embedding-based semantic recall works and how to configure the embedding API in its admin UI.
Prompt 4
Walk me through configuring a scheduled weekly AI review task in VaultEcho that summarizes my notes from a specific folder.
Prompt 5
How do I keep a desktop Obsidian vault and a VaultEcho-managed Headless Sync vault separate on the same machine?

Frequently asked questions

What is vaultecho?

An Obsidian-native gateway that turns structured input from automation tools like Coze or Shortcuts into Markdown notes, with semantic search and scheduled AI review.

What language is vaultecho written in?

Mainly JavaScript. The stack also includes JavaScript, Node.js, Docker.

How hard is vaultecho to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is vaultecho for?

Mainly vibe coder.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.