# Agent integrations

Use the agent where it runs best, and give it a scoped computer connection.

Status: Common API/MCP foundation · End-to-end compatibility pending

## Two deployment modes
**Remote agent:** Boardly, OpenClaw or Hermes runs elsewhere. It connects through ComputerUse's API/MCP broker and receives access only to the customer's selected rental. This is the recommended first integration because the agent lifecycle stays independent of desktop reboots.

**Hosted agent:** the customer's agent is installed inside the rental guest. Its state, channels, API keys and learned skills then become part of the customer workspace. Stopping an interactive chat does not necessarily stop a background gateway.

## One integration contract
Separate account-level management keys from per-rental execution leases. Revalidate ownership, project membership, active rental state and tool permission on every action. Do not expose host SSH or hypervisor access to an agent.

## Guides
- [Boardly](/docs/boardly/): attach an owned rental to a project and its authorized agents.
- [OpenClaw](/docs/openclaw/): configure the management MCP client and plan desktop access.
- [Hermes Agent](/docs/hermes/): configure the existing stdio bridge.
- [SDKs](/docs/sdks/): Python/JavaScript examples using implemented account endpoints.

## Model usage
Agents still need model-provider credentials and budgets. ComputerUse's rental price does not pay for unlimited tokens. Prefer short-lived scoped secrets, task budgets and approval for consequential actions.