Live data from Hacker News

Show HN: OzBrain, a shared brain for knowledge between agents and your team

ozbrain.com

51–60 of 73 posts

Re: Show HN: OzBrain, a shared brain for knowledge between agents and your team

#51
I use the LLM-wiki pattern for a structured directory of topic folders of .md files, and made it also compatible with the Open Knowledge Format [1].

My agent (Hermes) responds to a made-up command "vaultize this doc/link/text, etc" to add new .md files in the right format in the right place. The agent does a pretty good job of maintaining the index.md file, cross-links, etc.

A Quartz website builder creates a static site on my server, each MD file is a web page, and rebuilds when a new file is added [2]. This setup gives me a useful knowledge base with a great UX - across all the devices on my Tailnet, no need to run Obsidian Sync, or Syncthing.

This system is simple and works well, but i think it could maybe benefit from a memory system like Honcho to make it more effective as it scales.

[1] https://cloud.google.com/blog/products/data-analytics/how-th...

[2] https://quartz.jzhao.xyz/

Re: Show HN: OzBrain, a shared brain for knowledge between agents and your team

#52

A quick side note: I opened the page and my brain went into "It's an AI-landing-page there is no value there"-mode. That added quite a lot of friction to start reading it.

Noted! Thanks. I appreciate you getting thru it. What do you think would have made it more clear/faster?

Re: Show HN: OzBrain, a shared brain for knowledge between agents and your team

#53

A quick side note: I opened the page and my brain went into "It's an AI-landing-page there is no value there"-mode. That added quite a lot of friction to start reading it.

Me too. It demanded deep digging to find out how it was done and how is it different from other products. And my brain was resisting all the way through! I wish the author had made a mental image like “OzBrain is a Zettelkasten system built with AI background maintenance” then things will become much easier for the readers to understand.

Also thanks for doing the mental hurdling to get thru! I will work on that image...

Re: Show HN: OzBrain, a shared brain for knowledge between agents and your team

#54
post #48

A quick side note: I opened the page and my brain went into "It's an AI-landing-page there is no value there"-mode. That added quite a lot of friction to start reading it.

100%! It is a real mental block!

What do you think would improve that? Different language? More visuals?

Re: Show HN: OzBrain, a shared brain for knowledge between agents and your team

#57
post #33

nice :) > love to hear how you did it this is ours we built for Hedgy https://setoku.com our approach was to build a data lake that sucks company data into clickhouse and staple that to a knowledge store. this way the brain has a stream of live facts and builds knowledge around it. we gave up on trying to make the knowledge store human-readable -- i totally think there could be something there, but for now we just ca…

Cool. If I'm reading it right, it only allows read access? How do you get knowledge into the brain? I'm assuming that the content you put in is all agent driven. Source files (ie, a transcript, a data log, stuff that shouldn't eery change) get recorded but the articles are some kind of agent reasoning on top of it. I don't have any interface to edit an article. Your agent does it. And yeah I agree about not building…

for knowledge writes in setoku, any agent that does queries can propose knowledge or edits. edits are flagged for admin/curator review. agents can query the pending and confirmed knowledge but basically have a flag that tells them what's been "blessed".

i like your conceptual focus on not pairing it with data. for me, it's just a practical thing: i want one tool i can have a colleague (or my wife) install that adds all the context they'll need (and then one spot I can curate and govern that context).

Re: Show HN: OzBrain, a shared brain for knowledge between agents and your team

#59

This is interesting. Would you consider this a different type product/benefit than all the "memory" things we have seen popping up everywhere?. Is it different just because it lives in the cloud? To me it feels like a different thing than memory.

I think they’re similar but different. Memory is usually single user focused, a summary of specific facts or instructions. OzBrain is everything that was captured, reasoned, promoted, etc. and auditable record of what the latest thinking is and why. When agents are the primary user you need a way to capture why they ended up at where they ended up. Memory is more like the filtered summary of everything it has saved a…

Thanks!

Re: Show HN: OzBrain, a shared brain for knowledge between agents and your team

#60
Great entry point! I've also run into this issue and am trying to solve it.

But when I try this in different ways, a common issue is that the LLM often drifts. Sometimes it just drops important issues or records more trivial info than I need. Wondering how you solve this issue in OzBrain.

Post reply on HN