Feature Guide
HivemindOS is a control room for local agent fleets.
The feature surface follows the work an operator actually does: connect machines, configure agents, run work, preserve memory, manage money rails, and keep the local system healthy.
Each section below explains what the feature area is responsible for, which docs go deeper, and how the pieces connect in the running app. For the full visual pass, use the Diagrams And Maps atlas.
Control Room
The product starts with machines and agents. Fleet tells you what is online, which collectors are reachable, what runtimes and apps are available, and whether a machine is drifting from the expected setup. Agents and Chat turn those runtimes into configured workers with models, env, wallets, vault context, file attachments, and session history.
Fleet
Machine discovery, local and remote collectors, version drift, setup actions, active app badges, and hivenet API route catalogs.
Open FleetAgents, Runtimes, And Chat
Runtime profiles, model selection, adapter behavior, streaming chat, attachments, directory context, and phone-call handoff.
Open agentsCalling
Dashboard and mobile agent calls, BYOK Realtime by default, speaker-only fallback, phone pairing, and paid LiveKit/SFU cloud rooms.
Open calling docsWork Loop
Work is where operator intent turns into agent execution. The board captures rough ideas, promotes ready tasks, tracks claimed work, stores comments and run records, and turns finished output into deliverables. Scheduler adds repeated background work. Swarm and MiroShark handle rehearsal, simulation, and heavier analysis workflows.
Work Board And Scheduler
Kanban tasks, project provenance, Code Proof badges, agent dispatch, deliverables, schedules, machine-aware folder picking, background jobs, and work history.
Open work docsMiroShark And Runtime Gateways
Simulation templates, swarm rehearsal, run intelligence, route catalogs, and the minimal runtime-gateway integration points HivemindOS owns.
Open gateway docsCode Proof
Agent work gets messy fast if the only record is a chat transcript or a commit message. HivemindOS keeps the private trail: which task was opened, which project it belonged to, which machine handled it, and which agent touched it. GitLawb adds the part that code needs, signed provenance.
The goal is not to make every user manage a code node on day one. The normal path is quieter than that. HivemindOS can be Code Proof ready during setup, tasks can attach to projects, and linked projects can carry GitLawb proof metadata. If a project later needs local repo hosting, the deeper GitLawb node path is there.
That gives the Work board a better answer than “an agent changed something.” It can point to the project, the task, the machine, and the proof trail behind the code.
GitLawb Integration
The full integration guide for CLI setup, local DID identity, project links, proof badges, Fleet Code Node status, and lazy node hosting.
Open GitLawb docsWork Board Details
How project IDs and sanitized proof records move through tasks without leaking private vault paths, secrets, or machine details.
Open Work docsShared Brain
The shared brain is a normal Obsidian vault, not a proprietary database. HivemindOS writes durable state into that vault when available: Kanban records, notifications, scheduled runs, wallet records, shared skills, service notes, and reviewed outputs. GBrain indexes and retrieves. Syntho compiles reviewed Synthesis output. Trading Brain stays optional.
Brain, Vault, And Skills
Obsidian vault routing, graph access, shared skills, GBrain, Syntho, Trading Brain, Synthesis, and sync ownership.
Open brain docsHive Fusion
Capability search plus skill authoring: turn a normal prompt into a reusable shared-brain skill built from the agents, apps, tools, and workflows the hive already has.
Open fusion docsWhole Brain
The separated GitHub Pages guide for vault structure, brain services, shared skills, sync health, and architecture sync rules.
Open whole brainHivemind Sync
The cross-machine route for shared brain files, shared env keys, and vault-backed handoff transfers.
Open sync docsEnv, Files, Notifications, And Maintenance
Shared env, runtime file browsing, notification storage, process telemetry, and conservative repair checks.
Open system docsEconomy And Integrations
Wallet and token features are explicit rails, not a background permission pool. Agent wallets handle controlled Base and Solana balances plus x402 paid requests. UsePod is prepaid runtime access. Honey and Bankr HIVE are reward and claim paths. Integrations connect the control room to outside systems without making those systems own local state.
Wallets, Tokens, Honey, HIVE, And x402
Agent wallets, USDC sends, MoneyClaw, UsePod deposits, wallet-vault backups, Honey rewards, Bankr HIVE claims, and paid requests.
Open wallet docsMonetization
The free-vs-paid product boundary, including HivemindOS Cloud Agent Calls as a premium managed LiveKit feature.
Open monetizationIntegrations And Work History
GitLawb Code Proof, Nango, GitHub OAuth fallback, My Apps, API-service launchers, phone pairing, dynamic changelog, and work history.
Open integrationsNative And Background Surfaces
The browser and native app share the same Next.js UI. Tauri adds local filesystem and status helpers on This Mac, while AEON and Hermes keep their runtime-specific setup and background work docs separate.
Native App
Tauri development shell, packaged Next server, native status bridge, and desktop filesystem helpers.
Open native docsAEON Brain Access
GitHub Actions tailnet brain access with visibility-scoped policy and OIDC-gated brain endpoint calls.
Open AEON docsHermes Local Setup
Local Hermes runtime setup notes for running interactive agent work beside the HivemindOS dashboard.
Open Hermes docsFeature Map
flowchart TD
Fleet["Fleet"] --> Runtimes["Agents and runtimes"]
Fleet --> Apps["My Apps and API services"]
Runtimes --> Chat["Chat"]
Runtimes --> Phone["Phone calls"]
Chat --> Work["Work board"]
Work --> Scheduler["Scheduler"]
Work --> Deliverables["Deliverables"]
Work --> CodeProof["GitLawb Code Proof"]
Work --> History["Work history"]
Vault["Brain and vault"] --> Skills["Shared skills"]
Vault --> GBrain["GBrain"]
Vault --> Syntho["Syntho / Synthesis"]
Vault --> Notifications["Notifications"]
Vault --> Env["Shared env"]
Runtimes --> OpenClaw["OpenClaw"]
Runtimes --> MiroShark["MiroShark"]
MiroShark --> Swarm["Swarm theater"]
Runtimes --> Wallets["Wallets and tokens"]
Wallets --> UsePod["UsePod prepaid"]
Wallets --> TokenRails["Base / Solana / USDC"]
Wallets --> Bankr["Bankr HIVE"]
CodeProof --> Projects["Project registry"]