Show HN: Cabinet – Kb+LLM (Like Paperclip+Obsidian)

(runcabinet.com)

15 points | by Hilash 9 hours ago

10 comments

  • fawabc 1 hour ago
    really like the shipping of html apps inside knowledge bases, i can see a lot of very niche and useful internal tools being built to support a lot of custom workflows without leaving your actual knowledge base
  • subdomain 9 hours ago
    I love this idea! I agree that LLMs often don't have the knowledge that's actually important (a frustration I have with ChatGPT is that it remembers unimportant things and then over-indexes on them in its responses).
    • Hilash 9 hours 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 implicit inside the model. Curious if you’ve found any tools that handle this well today?
  • roitalpaz 9 hours ago
    why is this better than just using claude+obisidian?
    • Hilash 8 hours 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 source and free. plus, as an engineer I feel very uncomfortable running closed software these days,as one skill can take over my computer.
  • johnwhitman 8 hours ago
    [flagged]
  • eliluzac2 8 hours ago
    [flagged]
  • boazl 9 hours ago
    [flagged]
    • Hilash 9 hours 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.
  • alexkubica 9 hours ago
    [flagged]
    • Hilash 9 hours 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.
  • amirzak 9 hours ago
    [flagged]
    • Hilash 8 hours ago
      haha in 2027
  • Liav25 9 hours ago
    [flagged]
  • hanrok 9 hours ago
    [flagged]
    • Hilash 9 hours 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, optional hosted layer. Still early though. curious if you’re using it solo or already trying to share it with a team?