HivemindOS manual
Zero Human Companies
A Zero Human Company is a team of agents working toward one business goal, with you in charge of money, approvals, and whether it keeps running. Use it for repeatable work that should run like a small company rather than a one-off chat.
What a company is
Each company has:
- a charter and one main goal (the “apex goal”);
- a crew of agents, each with a role;
- budgets, approval rules, and a kill switch that you control;
- a cockpit where you watch its work, runs, and results.
The company runs on one of these engines:
| Engine | What happens |
|---|---|
| HivemindOS crew (default) | HivemindOS breaks the goal into Work Board tasks and routes them to the crew. Crew members can be agents on your machines, always-on Hivemind Bots, or a mix. With no agents set up yet, the company’s Queen does the work on HivemindOS itself, so a new company starts right away. |
| Hivemind Bot · first-party | One always-on Bot runs the whole company on a hosted schedule, with no Work Board tasks. It keeps working while your computers are off. |
| AEON background skill | One chosen skill runs in a linked AEON workspace. See Use AEON With Zero Human Companies. |
| Grok Bot · external handoff | HivemindOS prepares a reviewed company file and runbook. You set up and run the Bot yourself in Grok. |
Pick the crew engine when you need several roles handing work to each other on the Work Board. Pick a first-party Bot when one always-on agent can own the whole company.
A company opens on four tabs: Overview, Work, Results, and Setup. Turn on Advanced, next to Edit, to also show money, spending limits, analytics, team, learning, and labs. HivemindOS remembers the choice.
Start a company
- Open More → Companies and choose New company.
- Describe the business in one sentence, the way you would tell a friend — for example “funny cartoon videos posted to Instagram and TikTok every day” — or pick a ready-made business from the gallery.
- Check the Ready card. It names the company, shows what it does each day, and fills in where it posts, how often, and whether it asks you before each post goes out. Anything it picked up from your words is marked “From your description”. Change any of it with a tap; Fine-tune holds the look, feel, voice, video length, and your description.
- Choose where it runs: On this computer, or Always on to keep it working when your computer is off.
- Press Start.
Your description is kept word for word and every piece of work follows it, so a detailed idea (“a cartoon about aliens fighting leprechauns in space, silly with dry humour”) shapes every episode.
Nothing is posted, sent, or spent without your approval unless you turn that off. Posting stays reviewed by default: you approve each post with one tap until you switch Ask me before each post goes out off.
Turning it off lets the company post its finished videos and images on its own, but only to accounts you choose. On the company’s page, under Approvals → Where it posts, pick the company’s account on each platform (or connect one right there) and choose Let it post on its own for it; the company’s Overview shows the same choice until it is made. Each post then waits five minutes so you can cancel it, goes out within the account’s awake hours, and at most six go out on their own per account each day. Only files the company made in its own work folder post on their own. Its other finished videos and images wait for your OK, on the company’s Approvals tab and in Socials, where you can post them or not. For platforms that only take text, like X, Facebook and LinkedIn, the company keeps the finished file for you to post yourself. An account a company posts to goes out on its own only with that company’s work; anything else on it waits for you. Switching the company back to asking first, pausing it, deleting it, or removing an account sends its waiting posts back to you. Only you can make these changes; the company’s agents can’t.
Ready-made businesses
The gallery leads with businesses that run as a daily loop:
| Business | What it makes |
|---|---|
| AI Cartoon Channel | A short cartoon episode a day, with recurring characters and one consistent look |
| Faceless Reels Channel | Narrated short videos about your niche, with captions and matching visuals |
| Clip Channel | Captioned clips from long videos you are allowed to clip |
| Story Time Channel | Gripping stories, rewritten and narrated as short videos |
| Meme & Carousel Page | Original memes and swipeable carousels for your niche |
| Local Website Agency | Personalised website previews for local businesses, then the build or a monthly plan |
Client services (local search and reviews, ad videos), products (digital guides, a newsletter), and research (a competitor watch) follow. Posting to a platform needs that account connected; until it is, finished posts wait as ready-to-post files and the company asks you once.
Keep it running when your computer is off
Choose Always on when you start a company, or press Keep it running when this computer is off on an existing company. The company moves to its own always-on cloud computer, keeps the same goal and rules, and shows its results under Always on in Companies and on your phone. The copy on this computer stops planning, so nothing runs twice.
If your account has no always-on computer yet, you see its exact price first — what it costs per hour while running, about how much that is per month, the one-time setup, and the paused rate — and nothing is bought until you press Set it up and start. It is paid from your balance.
An always-on company posts from the cloud with its own accounts. As soon as it is set up, and under each company in Always on, Where it posts lists them: press Connect next to a network to sign in to that account in your browser, or Use an account you already connected. Take one away with its ✕; it stays connected for your other companies. Accounts a company used on this computer don’t carry over, so connect them once for the cloud. A network that isn’t open yet, or one always-on companies don’t post to (such as X), keeps the finished files for you. A company you set never to post to its own accounts keeps every finished post for you in the cloud too.
Ask me before each post goes out stays on unless you turned it off. Each post then waits under the company with its picture or video, title, caption and price; nothing is charged until you press Approve, Skip means it never goes out, and posts nobody checks are let go after 14 days. With it off, the company posts on its own, up to the number of posts a day you choose.
Make pictures and videos lets an always-on company that posts make the pictures and videos for its posts, paid from your balance. It is off for every company until you turn it on, right on the card as soon as the company is set up and under each company in Always on. Switching it on opens the daily limit: pick the most it may spend a day from the limits offered, read what you’re agreeing to right above Turn on, and only that press turns it on. The card shows what today has used and when the day ends in your own time; once the company reaches its limit, it stops making new ones until the next day starts. Change daily limit picks a new one the same way. Turning it off stops new pictures and videos at once; any already being made may still finish, within that day’s limit. If it was changed on another device while you were choosing, you’re told so before anything is saved.
Run it on another of your computers
A company can also keep working on another computer you own, such as a server you rent, at no extra cost from HivemindOS. On the company’s Overview, press Run it on another of your computers. HivemindOS lists your other connected computers and says, next to each one, whether it is ready or what it still needs. Every step happens right there:
- Set it up: prepares that computer to run companies. It updates and restarts HivemindOS there, which takes a few minutes. On a Linux computer this also keeps your companies running after a restart and with nobody signed in.
- Update it: that computer needs a newer version of HivemindOS first.
- Share from this computer: the company uses keys that computer doesn’t have yet.
- Add a teammate who works on that computer, when the company’s team only works on this one. Otherwise keep this computer on for them.
Pick a computer marked ready, press Move here, then confirm. The company’s goal, plans, history, memory, runs and spending records go with it, and it starts working there. It keeps working when this computer is off.
While it runs there, the company page says Runs on that computer and shows what it is doing. From here you can Start, Stop, Pause, Unpause or Bring it back here; the kill switch under Money → Treasury pauses it on that computer too. You can change its settings, team, budgets, products and limits from here too: each change is made on the computer that runs it, and the page shows it once that computer has it. If that computer can’t be reached, the page says so instead of changing only this computer’s copy. A few things still happen there or after you bring it back: letting the company do more without asking you, and deleting it. If that computer is off, or says it no longer runs the company, Bring it back anyway runs the company here from this computer’s copy; work done there since the move stays there, and the company page reminds you to tell that computer to stop once it is back online, so nothing runs twice. Until you have, the company can’t be moved again.
If a move stops part-way (for example because this computer restarted), the company page offers Finish moving or Finish bringing it back after a few minutes.
Good to know:
- The other computer needs at least 8 GB of memory. Next to a smaller one, HivemindOS offers the always-on cloud computer instead, with its price shown first. When you rent a server through HivemindOS, sizes with 8 GB or more are set up to run companies from the start.
- Work already started on this computer finishes here.
- The company’s own social accounts go with it, so it keeps posting there, and they come back with it. Their sign-ins don’t travel: an account that signs in with keys gets them when you press Share from this computer, and one you signed in to through this computer’s browser needs you to sign in to it again on that computer (the company page says which). Until then, its finished posts wait for you.
- Phones can’t run companies for you, and Windows computers can’t yet (they are listed, marked as not supported). A company that runs on one of your computers can move straight on to another with Move it to another computer on its page (from the computer that moved it there); to move it to the cloud, bring it back first.
More ways to start
Under More ways to start:
- Plan it in detail opens Founder Mode, which builds a reviewable blueprint and can import a shared company template.
- Set everything up myself opens the full form: identity, goal, engine, and crew.
- Bring in an existing project imports a repository or a data room (below).
Import an existing project
You can turn an existing project into a company without starting over. Choose a repository folder, review what HivemindOS finds, and create the company. HivemindOS records the project’s workflows and schedules (for example GitHub Actions, cron jobs, and hosting schedules) and shows them in the Systems tab.
You can also import a data room: a folder of plans, reports, spreadsheets, and other company documents. HivemindOS converts them on your machine and lists them in the Sources tab. Imported documents are treated as untrusted reference material. They cannot approve spending, launch work, or become standing instructions. See Documents And Brain Drop for supported file types.
Assign agents
One agent identity belongs to one company at a time. The company assignment controls that agent’s company budget, daily spend cap, approvals, mailbox, and work history, so sharing it between companies would make those controls unclear.
To reuse the same agent in another company, choose Duplicate agent in the crew picker. The copy gets its own identity and wallet but can keep the same model, runtime, skills, and personality. You choose whether to copy its environment, private memory, or chat history.
If an identity ends up in more than one company anyway, spending stops for it until you remove it from all but one.
Launch and stop
Every company has one start control, at the top of Overview and on the Board. What it does depends on the engine:
- HivemindOS crew: plans the goal into Work Board tasks. Later cycles wait until the board is idle and a crew member is free.
- Hivemind Bot: runs one cycle and sets up a hosted schedule on the Bot.
- AEON: sends the goal to the chosen skill. Later cycles wait until that workspace is idle.
- Grok Bot: there is no launch button. Prepare the handoff and set up the Bot in Grok.
To launch, a company needs a goal and an unfrozen treasury. The Bot engine needs a running Bot with managed credit.
With no agents set up. A company that runs on this computer works right away: when nobody else on its crew can take work, its Queen does the work on HivemindOS, using your free daily use. While it works that way:
- It plans a few tasks at a time and works on them one by one.
- A separate reviewer checks each finished task before it counts as done, the same way a crew member reviews another’s work.
- When today’s free use runs out, the company waits and picks up again on its own after the daily reset. It never uses your credits unless you allow it.
- To keep it working sooner, choose Keep working on credits on the company’s page. If you have no credits, the same place offers Add credits and keep working. You can take the choice back under Approvals.
- As soon as an agent or running Bot on the crew can take work, the company goes back to its crew.
If the Queen’s own setup can’t run on this computer, she works on HivemindOS’s free model for now, and the company page says so. She never does this when her model, or any crew member’s, keeps the work private or runs only on its own computer: the company’s page then says nobody on the crew can work right now, and lets you change her model right there.
Stop autonomy stops new work; work already in progress finishes. Freeze stops company spending. Launching also makes the machine you pressed it on the company’s home machine, so only that machine dispatches work. A company you moved to another of your computers is started and stopped from its Runs on band instead (see Run it on another of your computers).
Cadence. Existing companies repeat every 30 minutes by default. The always-on watcher templates start at 60 minutes. Shorten the interval only after results and provider limits justify it.
A stopped Bot stays on the crew but gets no work until you start it again in More → Hivemind Bots. Bot work uses your managed-agent credit.
Budgets and approvals
These controls govern the company’s native work:
- Treasury — budgets, spending, per-agent caps, recorded revenue, and the kill switch.
- Approvals — spending and actions waiting for your sign-off.
- Spend & limits — daily or monthly request and spend limits per provider or per operation.
Limits stack: a call goes ahead only if every limit that applies allows it. HivemindOS reserves the expected cost before a call, so a retry is not counted twice, and a frozen company is blocked before the call. Removing a limit keeps its history.
For Google Cloud, the same tab can find your projects, APIs, and billing accounts and set daily quota caps and a monthly billing budget. Daily quotas are hard caps enforced by Google. Billing budgets only send alerts; they do not shut anything off. Raising an existing limit asks you to confirm twice.
Some things are not covered by company budgets:
- AEON workspaces and Grok Bots use their own credentials and limits. Set spending limits with those providers. Grok Bots on one account share the same computer, files, and logins, so they are not separate security boundaries.
- A first-party Bot’s company budget is guidance, not payment authority. Unattended hosted spending needs a separately governed wallet or provider rail.
- External tools are not intercepted automatically.
Limits are local controls and estimates. Your provider’s billing records remain the source of truth.
Runs and proposals
The Runs tab records each important step the company takes: dispatches, task outcomes, preview reviews, revenue events, and replay requests. Each run keeps its input, status, events, and outputs.
Proposals are decisions waiting for you, such as a price change, a blocker that needs your input, a customer-preview decision, or a replay. Each proposal is marked pending, applied, rejected, or superseded, so you have a record of what the company suggested and what you chose.
A replay never redoes customer-facing or money-facing work silently. It creates a proposal, and you choose when to go ahead.
Results
- Deliverables shows what the company actually produced, such as live sites, published pieces, and videos. Scratch files and receipts go into a collapsed work log.
- Comms shows outreach threads and the crew’s mailboxes. It appears for companies that do outreach, and reads mail from AgentMail and Cloudflare Agentic Inbox. Create mailboxes in agent settings; see Apps And Agent Providers. If nothing is connected or no mail has arrived, the tab says why.
- Sales and Products show customers, pipeline, and fixed products for companies that sell.
- Analytics shows company performance. It can read a site from Hivemind Analytics or your own analytics account.
Every company task needs evidence before it counts as done. Product, design, content, and customer-facing work also needs review by a different agent. If evidence or a reviewer is missing, the task stops for your review.
Over time the company builds capability capital: reusable workflows, checks, receipts, and reviewed lessons that stay with the company even when its agents or models change. This is a summary of learned capability, not a money balance. Skill improvements the company suggests always need your approval before they are installed. See Agent Evaluations.
Connect bookings and CRM
- Bookings. Company agents can manage booking pages and appointments through Cal.com, Cal.diy, or Managed Hivemind Bookings. Each call must belong to an active company task, and changes need your confirmation. See Agent-Managed Bookings.
- CRM. Assign a Twenty workspace in the company’s Connections tab. Changes need an active task and your confirmation. See Twenty CRM.
Revenue Recording And Platform Fees
You can record revenue a company earns elsewhere, by amount and source. Revenue earned outside HivemindOS is not charged. Importing an existing project does not make its past or outside revenue subject to a fee.
A fee can apply only to a transaction HivemindOS itself supplies, bills, or hosts, and only under a disclosed policy enforced by HivemindOS servers. The app and manually recorded revenue cannot create a fee.
Record revenue automatically
Revenue can also arrive in the company ledger on its own. Each payment is counted once, even if it is re-sent.
- x402 product offers. Publish a product from the company catalog as a paid x402 endpoint. The server always charges the catalog price, and each settled purchase is recorded for the company. This follows the same self-hosted seller opt-in as the paid-agent gateway (
HIVEMINDOS_PAID_AGENT_SELLER_MODE=self-hosted). - Stripe. Point a Stripe webhook at
POST /api/company-revenue/stripe-webhook, and setmetadata.companyId(orclient_reference_id) on the payment link or checkout session. SetHIVEMINDOS_COMPANY_STRIPE_WEBHOOK_SECRET(orSTRIPE_WEBHOOK_SECRET). Only the settled amount is recorded.
For money goals, recorded revenue updates the company’s goal progress. The Treasury tab shows whether each revenue source is connected, and why not if it isn’t.
Advanced: Frontier Lab
Frontier Lab lets one small crew run more work in parallel, with every task reviewed and every token accounted for. You don’t need it to run a company. It requires the HivemindOS crew engine with the hierarchical process.
Models. It uses a fixed three-tier ladder through your OpenAI sign-in (OAuth), with no fallback to other providers:
- Scout —
gpt-5.6-luna: research, triage, and planning. - Builder —
gpt-5.6-terra: building, operations, and deployment. - Reviewer —
gpt-5.6-sol: independent review and QA.
You need a working OpenAI sign-in and at least two separate agents, so no agent reviews its own work.
Token budget. You set a monthly token ceiling. Before each task runs, HivemindOS reserves its token amount; afterward it records what was actually used. If usage can’t be measured, the full reservation is counted. Overages cut capacity to zero until the month resets or you raise the ceiling.
Scale stages. You choose the stage. Moving up requires proven results:
| Stage | Maximum parallel tasks | Tasks per cycle | Turns per machine | Evidence required to enter |
|---|---|---|---|---|
| Pilot | 4 | 4 | 1 | Starting stage |
| Team | 12 | 12 | 2 | 3 settled tasks at 67% success |
| Frontier | 24 | 24 | 4 | 12 settled tasks at 80% success |
Scaling down is always allowed. Scaling up is never automatic, and stages can’t be skipped.
Earned Scale. The cockpit compares your current stage with the one below it across outcome, proof, speed, tokens, unique contribution, duplication, human intervention, and reviewer disagreement. It needs at least three runs at each stage. It then recommends Scale, Hold, Reduce, or Collect evidence. A proof rate below 90% or any proof regression means Reduce. Moving from Team to Frontier requires a Scale result. The recommendation never changes your settings or spends tokens on its own.
To set it up, open a company, choose Frontier Lab, pick a token ceiling and limits, choose a stage, and save.