HivemindOS manual

Beeline Family Profiles

Beeline lets you set up a separate profile for each person you help, such as a parent or grandparent, so agents can act for them safely. Each card records who the person is, what you’re allowed to help with, and which browser and accounts belong to them.

Set up a family member

Create a dedicated Chrome profile for the person, and let them sign in to their sites directly where practical.
Add their Beeline card, with names they’re comfortable with, such as “mom” or “grandpa”.
Choose only the areas you need: calendar, healthcare, messaging, shopping, travel, or browser access.
Select their Chrome profile on the card. Start with Manual-first access.
Confirm authority only after the person agrees. You can revoke it later.
Optionally connect their Google Calendar or an MCP server from the card.
Optionally save a website login or API token for them in the desktop app.

Then just name the person in Chat, for example “Book my mom a doctor’s appointment.” If more than one card matches, the agent asks which person you mean. The agent sees only that card’s consent, allowed areas, and browser details.

Confirmed authority is not blanket approval. Bookings, purchases, messages, form submissions, and other important actions still need their normal review.

Browser access

Beeline uses a real Chrome profile for each person. It never imports that profile’s email, passwords, or cookies. Choose an access mode:

Manual-first opens the right profile so you can do the work yourself.
Trusted agent lets agents act in that Chrome profile through Browser Use. It needs Browser Use Full permissions and a confirmation for each action and website. The agent can see signed-in pages, so use this only for tasks and agents you trust.

Chrome opens in a visible window so you can watch. A profile can only be open once, so if Chrome is already running with it, quit Chrome completely and try again.

Saved logins and tokens

In the desktop app, you can save a website username and password, or an HTTP token, for one person. It goes straight into your operating system’s secure store: macOS Keychain, Windows Credential Manager, or Secret Service on Linux.

The card keeps only a label and the website address. There is no way to reveal or export the secret.
Agents can use the credential without ever seeing it. HivemindOS fills the login or sends the request for them, only to the exact saved website.
Turn on Extra-restricted agent use to require a confirmation on every use. HTTP tokens can also be limited to methods like GET or POST.

This keeps secrets out of agents, tools, and logs. It can’t protect against malware, a compromised computer account, or a malicious website. The website you log in to does receive the login. For high-risk accounts, use manual supervision and extra-restricted mode.

Password managers like KeePassXC or Bitwarden can be noted as the person’s login source. Beeline doesn’t read their vaults.

Calendar and MCP accounts

Google Calendar and MCP server connections are held by a HivemindOS-hosted service, which stores their secrets encrypted. It supports:

reading Google Calendar and creating events (with confirmation);
MCP server discovery, allowed reads, and tool calls (with confirmation);
safe retries, so a repeated request doesn’t run twice;
public HTTPS MCP servers only.

Enter MCP tokens yourself; they go straight to encrypted storage. If the hosted service is unavailable, these connections stay off and never fall back to your own accounts.

Removing a card

Removing a card deletes its saved logins and disconnects its hosted accounts first. If that cleanup can’t be confirmed, the card stays so you can retry. The app’s uninstaller also asks separately whether to delete Beeline’s saved logins.