Live data from Hacker News

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

ozbrain.com

41–50 of 73 posts

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

#41
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 human consumption. The agents create and consume vasly more data than we can.

I don't do any ingestion, I figure out can automate that in a routine or a zap or whatever you want.

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

#42
post #37
post #35

I have been looking for something like this but would actually want to self host due to the potential value/privacy of the data.

What's stopping you from putting your md files for agents right into your git repo along with the rest of your project files?

I would like to have more of a global memory for personal assistant type of agents. Auto updated and maintained. Browsable.

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

#43

I think the central question for a such memory system is whether we or the agents can find the relevant information and how to organize these data as changes continues to come in. Would we miss something in the retrieval process? How do we organize the information so they stay actual and correct without piling up the garbage? Of course we can continue to concatenate the data and tag them with version and date, but th…

What I'm building has a regular maintenance it runs across the knowledge. A. to chunk long articles down into smaller chunks or information with good routing. B. To review the latest thinking to make sure old thinking is deprecated and linked.

This will be the big challenge with this. Storing/Retrieving works fine across hundreds of articles... I have more than 500 right now just from OzBrain and a bit of the thing I was building before. When it becomes thousands with dozens being added all the time, the maintenance will become more of a necessity.

I lean a little bit towards store everything because the system's abilities are changing so fast right now, that having our previous thinking or reasoning is useful in being able to improve or correct current assumptions based on previous data.

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

#44
post #35

I have been looking for something like this but would actually want to self host due to the potential value/privacy of the data.

Yeah, I wouldn't put your crypto wallet into OzBrain or anything... this is more the day to day operation of your business or personal life. While that is also valuable, our data is already sitting on a lot of servers so might as well make it useful for you and your agents.

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

#47
How has traction been so far? And are there any valuable cross team/agent use cases you actually have experienced or are they theoretical?

I run https://smalldocs.org, which focuses on making Markdown a highly expressive space for agents (think slides, spreadsheets, charts, mermaid diagrams, etc.). I have built a local library which lives in the browser but reflects your local file system - explainer here: https://smalldocs.org/connect?return=%2Flibrary, demo here: https://smalldocs.org/library?demo=1. Which is pretty useful when you want to find local Markdown files.

However I am just about to introduce very similar functionality to yours - a cloud + agent access. Right now I don't know if this will actually be useful, but I think it will likely be something I can charge for. I have a few hundred developers that use SmallDocs on a weekly basis (https://smalldocs.org/analytics), but right now it's just a free local-first tool.

Code available here: https://github.com/espressoplease/smalldocs

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

#49

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.

Post reply on HN