Agent and RAG for Obsidian, Need Feedback

I just built this as a Personal/Portfolio project. I genuinely needed it, so I built it and I regularly use it.

I wanted to know if anyone else who uses Obsidian wants to use this too because right now its completely adapted to me.

For example, I use Ollama models to do everything. Everyone doesn't.

Honestly, feel free to give me feedback on this project. And if you would like to use it to, I will develop it further and make it accessible to all :)

GitHub Repo - Atrv-Shrn/Obsidian-Librarian

3 points | by athrv_shrn 10 hours ago

2 comments

  • athrv_shrn 8 hours ago
    I am using a system I designed on my own for the 'CRUD' style of thing for renames/deletions you are mentioning.

    People just hook up a Vector DB and store all the embeddings once and call it a day.

    I use three databases for the CRUD style system (idk its name, so i will just call it that lol).

    I use QDrant as the main DB, the one every RAG Pipeline requires, then I use Redis as a Raw storage for all the files and docs that are embedded and stored in QDrant already. Its like a totally raw db with the raw files.

    Then I used SQLite DB with timestamps and stuff to help with the "UPSERT" of new data (CRUD system) by looking at what changed against the DB as it already contains all the stuff from the last data sync.

    So in short, a normal RAG DB, a DB for raw info (helps with comparison during UPSERT), and a DB purely to judge where new data goes (CRUD system)

  • xspring1982 9 hours ago
    [flagged]