The conversation

pedalpeteHNSource authorAug 23

Building & toolsEditorial digest

An inbox, a branch, a review: a team knowledge workflow

pedalpete shares a Git-based knowledge system: drop material into an inbox, let an agent update documents on a branch, then have the author and affected teammates review the PR. Original inputs stay available, while Git records the changes.

Original excerpt
“I recently built our knowledge management system based (loosely) on the Karpathy LLM-Wiki model. I'm not sure I understand why it is so important”
Read the full original

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

Discuss

What was this responding to?

Parent context · original excerpt

dariusmonsefHNAug 21

I think agent-first chat interfaces will be a primary software modality and busy dashboard/UI will go away. I’m not sure who exactly wins it, but I want my knowledge to grow/go with me. A lot of the “knowledge” ie research, analysis, reasoning will be done by agents as the primary user. Our current notes tools & tasks management systems were built for humans… I don’t care what the 17th thing on my bug backlog is. I want to conduct agents that can execute for me and do great work. What I built OzBrain to do: + Create a central place for agent reasoned knowledge to live + Be agnostic about what apps/agents connect to it + Capture everything and…

Full original

Community replies 0

No community replies yet. Add your perspective.

Replies from the source 0

Direct replies available in this import. Original-language excerpts.

This sample contains no direct replies. Follow the source to read the full discussion.

Continue on Hacker News

Respect different perspectives. Share concrete experiences.