Skip to main content

HiveMind

Daemon for syncing agentic coding sessions to W&B.

Installation

# Recommended (macOS Apple Silicon + Linux)
curl -fsSL https://hivemind.wandb.tools/install | sh

# Via Homebrew (macOS)
brew install wandb/taps/wandb-hivemind

# Any platform, incl. Intel Macs and Windows
uv tool install wandb-hivemind

Usage

# Run the daemon (watches for new sessions)
hivemind run

# Check status
hivemind status

# Fork a previous session
hivemind fork <session_id>

# View logs
hivemind logs
hivemind logs -f  # Follow logs

Authentication

# Login (auto-detects best method)
hivemind login

# Check authentication status
hivemind whoami

# Logout
hivemind logout

Importing Existing Sessions

For development or initial setup, import existing sessions:

# Import ALL sessions found on disk
hivemind import

# Import sessions from the last 24 hours
hivemind import --since 1d

# Import sessions from the last 2 hours
hivemind import --since 2h

# Import sessions since a specific date
hivemind import --since 2024-01-15

# Dry run to preview what would be imported
hivemind import --dry-run

# Import from specific paths
hivemind import --path ~/projects/myapp

# Custom endpoint override
hivemind import --endpoint https://api.example.com

Force Re-sync

If you need to re-import all sessions for a specific agent (for example, after fixing sync issues or to apply updated normalization):

# Re-sync all Cursor sessions
hivemind resync cursor

# Preview what would be deleted
hivemind resync cursor --dry-run

# Skip confirmation prompt
hivemind resync cursor --yes

Supported agent types: claude, claude_web, cursor, codex, gemini, opencode

Warning: This permanently deletes your session data from the server. The data will be re-imported from your local session files.

Rate limiting: You can resync each agent type once per hour.

Configuration

Configuration file: ~/.hivemind/config.toml

# View current config and where values come from
hivemind config show

# Set endpoint (e.g., for QA testing)
hivemind config set server.endpoint https://hivemind.qa.wandb.tools

# Get a specific value
hivemind config get server.endpoint

# Reset to defaults
hivemind config reset

# Show config file path
hivemind config path

Example config file:

[server]
endpoint = "https://hivemind.qa.wandb.tools"

Configuration Priority

Settings are resolved in this order (highest to lowest):

  1. Config file (~/.hivemind/config.toml) - user's explicit preference
  2. Environment variable (HIVEMIND_ENDPOINT) - for testing/CI overrides
  3. Default (https://hivemind.wandb.tools)

The daemon automatically reloads when the config file changes.

Environment Variables

  • HIVEMIND_ENDPOINT - Backend API endpoint (overridden by config file)
  • HIVEMIND_IMPORT_SINCE - Default --since filter for imports

Troubleshooting

Resync Issues

"Cannot modify state: daemon is running" The resync command will automatically signal the running daemon. If you see this error, the signaling mechanism may have failed. Try stopping the daemon and running resync again.

"Rate limit exceeded" You can only resync each agent type once per hour. Wait for the time shown in the error message.

"Backend cleanup succeeded but local state update failed" Your server data has been deleted. The path to your state.json file is shown in the error. You can manually remove the sessions for that agent type, or simply restart the daemon - it will re-discover and re-sync all sessions.

Metadata

Release files for wandb-hivemind 1.0.7

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for wandb-hivemind 1.0.7
File Interpreter ABI Platform
wandb_hivemind-1.0.7-py3-none-any.whl Python 3 none any Details

Release files / wandb_hivemind-1.0.7-py3-none-any.whl

Download URL wandb_hivemind-1.0.7-py3-none-any.whl
Size 392.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
d9c441199271c35718e5729cdffcddda06616c25b0d4e216ed4019e1e0e5d41c
BLAKE2b-256 checksum
How to use checksums
b5f390b87926e51cc19772adbf430286d5d67ff75be7c18110dc0eb41666b16b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 26, 2026.

Transparency log

Release history Release notifications | RSS feed

1.1.0

1 release file

1.0.8

1 release file

This release

1.0.7 This release

1 release file

1.0.6

1 release file

1.0.5

1 release file

1.0.4

1 release file

1.0.3

1 release file

1.0.2

1 release file

1.0.0

1 release file

0.7.14

1 release file

0.7.13

1 release file

0.7.12

1 release file

0.7.11

1 release file

0.7.8

1 release file

0.7.7

1 release file

0.7.6

1 release file

0.7.5

1 release file

0.7.4

1 release file

0.7.3

1 release file

0.7.2

1 release file

0.7.1

1 release file

0.7.0

1 release file

0.6.11

1 release file

0.6.9

1 release file

0.6.8

1 release file

0.6.7

1 release file

0.6.6

1 release file

0.6.5

1 release file

0.6.4

1 release file

0.6.3

1 release file

0.6.1

1 release file

0.6.0

1 release file

0.5.4

1 release file

0.5.3

1 release file

0.5.2

1 release file

0.5.1

1 release file

0.4.3

1 release file

0.4.0

1 release file

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page