Built with Claude. Disclosure: I work on Hivemind. Per the subreddit rules, posting with a full description of what it is and how it works. What it is Hivemind is an open-source Claude Code plugin. It installs into Claude Code, watches the traces from your sessions, finds patterns you repeat, and crystallizes them into reusable skills that show up as native slash commands in Claude Code. Because it’s a plugin and not an external tool, the skills it generates drop in as proper Claude Code slash commands. No external tool calls, no separate config files to maintain. What it does in practice Every morning for about a week, I was writing the same long prompt to Claude Code to pull together a team standup review. Same structure, same context blocks, slightly different details each day. I never thought to turn it into a custom slash command. Hivemind noticed the pattern and built /team-standup for me on its own. I didn’t configure it or ask for it. It watched the repeats and creates the skill. The thesis: agents should compound Most “memory” tools for coding agents are bolt-on chat history. Hivemind is different in two ways: It reads traces, not chats. The signal is what the agent actually did, not what was said. It writes skills, not notes. Patterns get turned into Claude Code slash commands that live in your project, get versioned, and improve over time. The agent is more capable next week than it was this week. That’s the whole point. Skill governance is the real work Generation is the easy part. The interesting problem is what happens after a skill exists. Hivemind handles four states explicitly: Candidate. New patterns get proposed as candidates with the triggering trace examples attached. They don’t show up as slash commands until they’ve fired correctly a couple of times. Promoted. Once a candidate proves itself, it gets written into your project as a real slash command. Drift detection. When the underlying patterns in the traces stop matching the skill, Hivemind flags it and proposes an update. This is the part most “skills” workflows skip and it’s why hand-written skills go stale. Retirement. Skills that aren’t being used get archived so the active loadout stays clean. Scope is per-project by default. Skills are tied to the conventions of the repo they were learned in. You can opt in to global skills, but the default avoids the failure mode where a local habit looks like a universal rule. Privacy, upfront Traces are processed in Deeplake Cloud by default, with strict access controls and privacy protections. If you want full control, Hivemind supports self-hosting. Set the trace endpoint to your own infra and nothing leaves your machine. The self-host path is in the README. DM me if you want help wiring it up. Skills from real usage A few that Hivemind has generated for me and my team at Activeloop: /team-standup: pulls recent commits, open PRs, and stuck threads into a structured standup brief. The one that started this whole project. /db-debug: environment-aware database debugger. Knows our dev vs prod clusters, picks the right kubectl context, runs the right diagnostic queries for whichever cluster you’re on. /posthog-sdk-test: runs our PostHog SDK integration test sequence with the right event payloads and verifies them in the dashboard. /release-notes: diffs against the last tag, groups commits by area, drafts release notes in our format. None of these were configured. They emerged from repeated traces. How it works under the hood Three pieces: The plugin hooks Claude Code session events and captures task traces. Every N messages, a step reads recent traces and decides whether to propose a new skill, update an existing one, or do nothing. Promoted skills get written back as Claude Code slash commands. The trace aggregation step is itself running on Claude Code with a meta-skill that knows how to read traces and write skills. The harness improves the harness. That’s the direction we’re going. Team propagation If multiple engineers on your team have Hivemind installed and point at a shared trace store, skills propagate. I built /team-standup once. Every engineer on our team has it now. Nobody copied anything. This matters more than it sounds because the median engineer never writes their own slash commands. With Hivemind, one engineer’s good pattern becomes the team’s tooling. Install Open source, free. npm install -g @ deeplake/hivemind && hivemind install Repo: https://github.com/activeloopai/hivemind Happy to get into the logic, the drift detection heuristics, the self-host setup, or where this goes next. The thing I’m most interested in talking about is the meta-harness direction: whether harnesses end up as fixed procedural code or as agents that continuously improve their own tooling. We’re betting on the second. submitted by /u/davidbun
Originally posted by u/davidbun on r/ClaudeCode