Hivemind Bots

A Hivemind Bot is an always-on HivemindOS agent that runs in the cloud. It has its own persistent browser computer, scheduled and event-driven routines, approvals, human takeover, managed model access, and cloud-safe integrations.

Use a Bot when the work must keep running while your computers are off. For interactive work or private local files, an agent on your own machine is usually simpler and cheaper.

Create a Bot

1. Open More → Hivemind Bots.
2. Choose Deploy agent and review the size, storage, running price, stopped price, and setup cost.
3. Name the agent and fund only what you plan to use.
4. Wait until it reports healthy, which can take a few minutes.
5. Connect Hive Superbrain, your private machine network, or external tools only if the agent needs them.

Costs and funding

Prices and availability can change, so HivemindOS loads current plans, rates, and balances from the managed service when you review or fund a Bot. Trust the confirmation screen, not an old table or a local setting.

When you fund from a wallet, HivemindOS shows the network, asset, amount, recipient, expiry, and expected credit before your wallet signs. Normal wallet rules apply: spending must be on, limits must allow the amount, company budgets and freezes apply to company work, an approval threshold can pause the payment, and the same payment can’t be credited twice.

Running out of credit stops compute instead of running up a balance. Every Bot turn uses managed-agent credit.

Start, stop, and delete

The workspace lives on persistent storage.

• Stop removes active compute to save cost but keeps the workspace, its identity, and the connections you kept.
• Start brings up fresh compute around the same workspace.
• Delete permanently removes the compute and workspace. It cannot be undone.

Before deleting, export important files, stop schedules that point to the Bot, reassign company work, and check it isn’t the only copy of any paired data. Your local Hive Superbrain is not affected.

The persistent computer

Each Bot has a browser whose cookies and sessions survive stops and restarts. Use the Computer tab to watch it or step in:

1. Load the screen in view-only mode.
2. Choose Take over to pause the agent.
3. Click, type, scroll, or navigate on the screenshot.
4. For a password, pick the field and use Enter without saving. The value goes only into that field and is not stored.
5. Release takeover so the Bot can continue.

Takeover expires after one minute unless the open panel renews it. Treat screenshots like a live screen share.

Policy and approvals

In the Policy tab you can allow or deny domains, require approval for risky actions or for everything, and turn on an independent model review.

Denied domains always win. Actions that look like sending, publishing, buying, transferring, deleting, installing, uploading, changing an account, or accepting terms pause for approval. Each approval covers one exact action; a changed action needs a new approval. Pending approvals also appear in Alerts.

An approval can allow one click at a checkout, but it does not enforce budgets, check a recipient or amount, or unlock your local wallet. Keep provider caps, wallet limits, and payment confirmations on. Deploying a Bot does not enable unattended spending.

Hosted routines

The Routines tab runs work on its own:

• Schedule: a five-field cron expression in the timezone you choose.
• Event: a named event such as company.lead.created, with a stable event id so retries aren’t run twice.

Each routine has a prompt, runtime limit, pause control, Run now, and recent run receipts. The prompt is stored so it can run while you’re offline, so never paste credentials into it. Raw event data and model responses aren’t kept in the routine log. Failed routines raise an Alert.

Test a routine with Run now before scheduling it.

Use a Bot for a Zero Human Company

• Run the whole company: choose Hivemind Bot · first-party as the company’s autonomy engine and pick a Bot. Launching sends the company’s goals, catalog, budgets, and approval rules (never your personal details or credentials), records the first run, and creates a company routine. Existing companies default to 30 minutes between cycles; some watcher templates start at 60 minutes. Stop autonomy, Freeze, or deleting the company stops future cycles.
• Fill one crew role: add the Bot to a HivemindOS crew like any agent. It picks up Work Board tasks for its role, so a multi-role company can run with no personal machine online. A stopped Bot is skipped, and specialist agents on your machines are picked first for tasks that need them.

Grok Bot · external handoff is different: HivemindOS can only produce a reviewed template and runbook for it.

See Zero Human Companies.

Hive Superbrain in the cloud

Bots don’t get your brain automatically. You can pair a Bot with an approved Hive Superbrain sync peer so it can work while your machines are off and sync back later. Review what the vault contains first, and keep plaintext secrets out of it. Credentials you add to a Bot are stored by the managed service, not copied from your laptop.

What works when your computers are off

App projects

A running Bot can host app projects in its workspace. In the Bot panel’s App Projects section, pick a host: Your computers (projects are created from Chat) or a Bot. On a running Bot you can create a project from the Next.js starter, start or stop it in an isolated container, and delete it; each asks for confirmation.

Current limits:

• There is no live preview yet. Publish through Hosting to view a site.
• A Bot deployed before app controls existed must be reconfigured once; the panel tells you.
• Start, stop, and delete for cloud-hosted projects arrive in a later release. The App Builder view currently builds on local and fleet machines.

See App Builder before publishing anything.

Remote access

The Bot panel works on small screens and uses the same signed-in HivemindOS connection as the rest of the dashboard. Never expose the local dashboard or a Bot’s endpoints to the open internet.