Integrations, Apps, And Work History

HivemindOS connects agents to outside services without making those services the owner of your local control room. It also keeps a readable history of managed work so important results are not buried in one chat or terminal session.

Connect An App Or Account

Open More → Integrations to see available connections. Each card shows whether the service is connected, which account is in use, what setup is missing, and whether the live connection check passes.

1. Choose the service.
2. Review the access it needs and the kinds of actions it can perform.
3. Complete the provider sign-in or enter the requested credential in the setup field.
4. Wait for HivemindOS to verify the connection.
5. Return to the task or conversation that needed it; the current surface refreshes in place.

Connections can include GitHub, Google, Linear, Slack, Notion, Microsoft Azure, Twenty CRM, messaging and social accounts, and compatible agent or tool providers.

What A Connection Allows

A connected account is not blanket permission for every agent and every action.

• Read and write operations remain distinct.
• The selected agent and current task still determine relevance.
• Publishing, sending, deleting, spending, and account changes can require confirmation.
• A Zero Human Company can add its own budget, integration limits, and approval policy.
• The provider’s scopes and account permissions remain in force.

HivemindOS can show agents that a required credential is set without returning its plaintext value. Shared setup can be reused across trusted machines through Shared Env.

Use Apps And Services Across The Hive

Open More → Apps & Services to see compatible apps and APIs discovered on connected machines.

• An interactive app opens in its normal interface.
• A service card explains what the service offers and whether it is healthy.
• The machine label tells you where it is running.
• Offline apps remain unavailable until their owning machine reconnects.

Discovery does not bypass authorization. An agent still needs the appropriate connection, machine permission, and task approval before using a service.

GitHub And Code Proof

GitHub connections support repository work such as issues, pull requests, workflows, and agent coding tasks. Use the normal in-app sign-in when available; use a personal token only when that setup path is appropriate for the account.

GitLawb Code Proof is a separate optional integration for signed code provenance. It can link HivemindOS projects to proof records without placing private vault paths, secrets, or machine details into the public proof. See GitLawb Code Proof.

Work History

Open History to review managed work that has been recorded across projects and agents. You can search, filter by project, and move through older entries.

History is useful when you need to answer:

• What changed recently?
• Which project or task produced this result?
• Where is the deliverable?
• Which agent or managed run handled the work?
• Was the work completed, blocked, or still awaiting review?

History is a navigation and audit aid, not proof that an unobserved action succeeded. Consequential managed work should still carry a receipt, resulting artifact, provider response, or evaluation appropriate to the task.

Phone And Messaging Connections

Calling and messaging are integrations too. Pairing a phone or adding a channel lets agents reach you or send approved updates, but it does not automatically enable outbound contact for every agent.

Use Calling for voice setup and the Messaging view for Telegram, Discord, iMessage, and other available channels. Keep personal and company communication identities separate where the account or approval policy requires it.

Disconnect Safely

Before disconnecting an account, check whether it is used by an enabled automation, active company, cloud agent, or unfinished task. Disconnecting stops new calls through that connection; it does not undo actions already completed at the provider.

Removing a shared credential should also sync as a removal to trusted machines. If an offline machine still reports the old setup after reconnecting, review Hivemind Sync and Troubleshooting.