Show HN: Agentlore – searchable team log for AI coding agent sessions

Show HN: Agentlore – searchable team log for AI coding agent sessions(github.com)

2 points by clkao 119 days ago | 1 comment

Agentlore syncs your team's AI coding agent conversations to shared storage, links them to git commits and PRs, and makes them searchable. Built on top of agentsview[0] by Wes McKinney, which indexes local sessions from various coding agents into a SQLite database.

I built this because I wanted to understand my own agent usage patterns. I mostly use Claude Code, and agentsview was already doing the hard work of collecting sessions locally.

Then I wanted to sync sessions across my machines so everything was searchable in one place. When I found interesting new approaches with coding agents (superpowers, gsd, higher-order prompting) that I wanted to share with friends and teammates. I ended up creating gists, which is a terrible way to share conversations.

These clicked together into agentlore. A daemon watches agentsview's local database, masks secrets, and syncs conversations to ClickHouse. A web UI lets you browse, search, and filter across all your sessions.

The part I'm most excited about is git linking. Agentlore parses tool calls for git commit and gh pr create invocations, extracting commit SHAs and PR URLs. So you can go from a commit to the full conversation that produced it. Every conversation gets a shareable permalink, so you can drop it in a PR comment or Slack and people can see exactly what happened.

What I'm hoping to see play out:

- Review agents should get more accurate when they have the conversation context, what was intended and what was manually tested, not just the diff. - People can learn from each other. Someone figures out a better way to prompt for refactoring, the whole team can see how they did it. - Context stops disappearing. When you pick up code someone else wrote with an agent, the conversation is right there instead of lost on their machine.

This is early and likely broken in places. Would love feedback.

Demo: https://demo.agentlore.io/sessions/589b7dd5-93ad-4dc0-8e6f-d... (the conversation the built this project. you can see all subagent sessions, but not all commits are captured yet)

[0] https://github.com/wesm/agentsview

nachocoll 115 days ago |

The commit-to-conversation linkage in Agentlore is the feature that matters most. Every review of AI-assisted code has the same problem: the diff shows what changed, but not why, and not what the agent was doing when it generated that specific change. Without the conversation log linked to the commit, you're reviewing output without context.

"Context stops disappearing" is exactly the right framing. Right now, the tacit knowledge about how a piece of code was generated — what the developer was trying to accomplish, what alternatives the agent suggested, what the developer rejected and why — evaporates when the session ends. It's a systematic loss of institutional knowledge.

The Agile Vibe Coding Manifesto makes "traceable intent over opaque implementation" a core value precisely because this is the critical accountability gap in most AI coding workflows. Agentlore is filling that gap at the session level. The aspirational version of this is every AI-generated change in a PR having a linked, reviewable conversation that explains the intent.

The "people can learn from each other" use case might end up being as valuable as the review use case: https://agilevibecoding.org