diff --git a/hivemind.mdx b/hivemind.mdx index 4121b00ff7..6cb032bf2e 100644 --- a/hivemind.mdx +++ b/hivemind.mdx @@ -62,10 +62,11 @@ After the HiveMind service starts receiving information from your team, access t From the HiveMind dashboard, your team can: -- **See sessions across agents**: One daemon captures sessions from every supported agent, with no per-agent configuration. +- **See sessions across agents**: One daemon captures sessions from every supported agent, with no per-agent configuration. A session that an agent starts as a subprocess is linked to its parent, so fan-out appears as a tree rather than as unrelated sessions. +- **Organize and filter sessions**: Attach key-value labels and tags to a session, then narrow the **Sessions** page to what you care about. A set of `hivemind.*` labels is derived from every session automatically, so filtering is useful before anyone tags anything by hand. To tag the session you're in, run `hivemind tag`. You can also edit tags from the **Labels** card in the session insights sidebar. To let a coding agent tag its own session, install the `hivemind-tag` skill. For details, see [Labels and tags](https://hivemind.wandb.tools/docs/labels) in the HiveMind documentation. - **Track spend and usage**: View estimated cost over time, cost by model and team, token usage, and cost per merged pull request. Cost figures are estimates from published model pricing and session token counts, not billed amounts from your AI vendors. To report your own token usage and cost from the command line, run `hivemind usage`. - **Measure outcomes**: Connect agent activity to pull requests, merge rates, and how much agent-written code survives. -- **Track skills and slash commands**: See which skills and slash commands your team invokes and how widely they're used. +- **Track skills and slash commands**: A sortable, paginated table shows what your team invokes and how widely each one is used, with category badges and multi-select category filters. Preview a definition, then copy or download it. - **Reuse past work**: Use `@hivemind` inside Claude Code, Codex, or Cursor to search your team's session history and bring relevant context into your current session. - **Learn from history**: Import existing sessions from local tools like Claude Code or Cursor to gain new insights from prior AI usage. diff --git a/images/hivemind/hivemind-recent-sessions.png b/images/hivemind/hivemind-recent-sessions.png index cdc1152338..3743be1eee 100644 Binary files a/images/hivemind/hivemind-recent-sessions.png and b/images/hivemind/hivemind-recent-sessions.png differ diff --git a/images/hivemind/hivemind-skills.png b/images/hivemind/hivemind-skills.png index 4404719c18..132c4cdddf 100644 Binary files a/images/hivemind/hivemind-skills.png and b/images/hivemind/hivemind-skills.png differ