Hilash

4 ms·

1. 1.▲
   by Hilash 6mo ago

   haha in 2027
2. 2.▲
   by Hilash 6mo ago

   thanks!
3. 3.▲
   by Hilash 6mo ago

   obsidian is overkill for most people. however, if you are managing more than private repo, you would like to see one place for your ai agents + data, a KB +LLMs. Also, Cabinet is open source, it’s like Paperclip+obsidian together, open sour
4. 4.▲
   by Hilash 6mo ago

   glad you liked it! Yes, I’m thinking about org support, but trying to do it without losing the “files on disk / git-backed” model. directions i'm thinking about: shared knowledge base (still file-based), permissions on top, optio
5. 5.▲
   by Hilash 6mo ago

   yes, Cabinet core principle is BYOAI (Bring your own AI). Cabinet should work with Claude, Codex, OpenCode, local models, and whatever comes next, without forcing your knowledge into a single provider’s ecosystem.
6. 6.▲
   by Hilash 6mo ago

   Thanks! It's just 2 days old and i'm working full speed to merge all PRs. it's really exciting have my first open source project after years in corporates.
7. 7.▲
   by Hilash 6mo ago

   Totally agree. The current memory implementations feel a bit meh. you don’t really control what’s stored or how it’s used. I’ve been thinking of it more as a visual knowledge layer you can inspect + operate on, rather than something implic
8. 8.▲
   Show HN: Cabinet – Kb+LLM (Like Paperclip+Obsidian)(runcabinet.com)

   16 points by Hilash 6mo ago|11 comments