展开讨论

构建与工具编辑摘编

收件箱、分支、审查:团队知识库的小工作流

pedalpete 分享了团队知识库的做法:先把材料放进收件箱,agent 开分支更新文档、时间线,再由作者和受影响的同事审查 PR。保留原始输入,用 Git 记录修改,让知识更新沿用团队熟悉的协作流程。

原文节选

“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”

阅读完整原文
源讨论Show HN: OzBrain, a shared brain for knowledge between agents and your team
讨论

这条内容在回应什么?

父级讨论 · 原文节选

DA

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…

完整原文

社区评论 0

还没有社区评论,来聊聊你的看法。

原讨论中的回复 0

仅展示本次导入中包含的直接回复,原文节选。

本次样本未包含直接回复,可以前往 Hacker News 继续阅读。

在 Hacker News 阅读

尊重不同观点,分享具体经验。

登录后即可发帖、评论、转发和引用。