Hivemind Manager
Hivemind Manager (hm) is a developer-focused process manager built on top of Hivemind.
It provides service discovery, dependency management, supervision, automatic restarts, log management, and project-aware workflows for local development environments.
Instead of manually managing multiple Hivemind processes, hm treats your workspace as a collection of services and provides a unified CLI for operating them.
Features
- Automatic discovery of
*.hmservice definitions - Project-aware workspace detection
- Dependency resolution via
# depends_on: - Supervisor process with automatic restart backoff
- PID tracking and process lifecycle management
- Orphaned process cleanup
- Multi-service log management
- Execution-based log rotation
- Project-local configuration via
pyproject.toml - Works from any subdirectory inside a project
- Lightweight and Hivemind-compatible
Installation
From PyPI
pip install hivemind-manager==0.1.0
From Source
git clone git@github.com:dhruv13x/hivemind-manager.git
cd hivemind-manager
pip install -e .
Requirements
- Python 3.8+
- Hivemind installed and available on
PATH
Verify installation:
hivemind --version
Quick Start
Inside your project:
hm init
This creates a project configuration:
[tool.hm]
home_dir = "hm"
preserve_logs = true
max_log_history = 5
max_log_size_mb = 0
Then start services:
hm up
Check status:
hm ps
Stop everything:
hm down
Service Definitions
Services are defined using standard Hivemind files.
Example: infra.hm
api: uvicorn app.main:app --host 0.0.0.0 --port 8000
worker: python -m app.worker
Example: transfer.hm
# depends_on: infra
transfer_bot: python -m services.transfer_bot.main
Dependency Management
Dependencies are declared using comments:
# depends_on: infra
When starting:
hm start transfer
hm automatically starts:
infra
└── transfer
if the dependency is not already running.
Project Discovery
hm automatically discovers project roots using:
HM_PROJECT_ROOTpyproject.tomlcontaining[tool.hm].hmservice definitions- Current working directory
Commands work from anywhere inside the project:
cd scripts/dev
hm ps
hm start infra
hm logs transfer
Commands
Initialize Project
hm init
Create project configuration and HM workspace.
List Services
hm list
Example:
Detected services:
✓ infra
✓ transfer
✓ bypass
✓ uab
Show Status
hm ps
Example:
SERVICE STATUS
----------------------
infra running
transfer running
uab stopped
Start Service
hm start infra
Without log following:
hm start infra --no-follow
Stop Service
hm stop infra
Restart Service
hm restart infra
Without log following:
hm restart infra --no-follow
View Logs
hm logs infra
hm uses Inode-aware tailing, meaning the log stream persists across service restarts and rotations. You don't need to re-run the command when a service cycles.
Start All Services
hm up
Start all and follow combined logs:
hm up --follow
Stop All Services
hm down
Diagnostics
hm doctor
Example:
Project Root : /workspace/bot_platform
HM Home : /workspace/bot_platform/hm
Config File : /workspace/bot_platform/pyproject.toml
Hivemind Bin : /usr/local/bin/hivemind
Log Management
Each service receives:
hm/
├── infra.log
├── infra.log.1
├── infra.log.2
├── infra.pid
Execution-based rotation preserves previous runs:
infra.log— current executioninfra.log.1— previous executioninfra.log.2— older execution
This makes debugging service restarts straightforward.
Configuration
Project configuration lives in pyproject.toml:
[tool.hm]
home_dir = "hm"
preserve_logs = true
max_log_history = 5
max_log_size_mb = 0
| Option | Description |
|---|---|
home_dir |
Directory used for logs and PID files |
preserve_logs |
Preserve previous execution logs |
max_log_history |
Number of historical logs to keep |
max_log_size_mb |
Size-based rotation threshold (0 disables) |
Environment Variables
Override configuration via environment:
| Variable | Purpose |
|---|---|
HM_PROJECT_ROOT |
Override project root detection |
HM_HOME_DIR |
Override logs/PID directory |
HM_HIVEMIND_BIN |
Override Hivemind binary path |
Why Hivemind Manager?
Hivemind excels at running processes.
Hivemind Manager adds:
- Service-level supervision
- Dependency resolution
- Project discovery
- Log history
- Process cleanup
- Workspace-aware workflows
without replacing Hivemind itself.
License
MIT License
Copyright (c) dhruv13x
Metadata
Release files for hivemind-manager 8.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| hivemind_manager-8.0.0.tar.gz | 25.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| hivemind_manager-8.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 46.3 kB
Release files / hivemind_manager-8.0.0.tar.gz
| Download URL | hivemind_manager-8.0.0.tar.gz |
|---|---|
| Size | 25.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f9814783ddb5b05de4acef3db3313f350fa13c06e29fea8b2acd73d26ed95049
|
|
BLAKE2b-256 checksum How to use checksums |
538d4875beaad4d55ee14990c6446ee7f50fdbd2d820dd9d9dfffaed7d9bfe69
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 18, 2026.
Transparency logRelease files / hivemind_manager-8.0.0-py3-none-any.whl
| Download URL | hivemind_manager-8.0.0-py3-none-any.whl |
|---|---|
| Size | 20.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ac311e7aeb237f54b9cca42d85fd9e545f07f640c91ea6f3ceee5bc01a02ccea
|
|
BLAKE2b-256 checksum How to use checksums |
282349417d18d7c501868978523da11116469a1d0953187160ae18d1f13facdf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 18, 2026.
Transparency log