Skip to main content
Private Beta — Contact us to get set up.
Autonomous Char runs unattended in a cloud browser—without user presence or a local machine. It connects to the Tool Hub and has access to all tool sources: internal MCP servers, external MCP servers, and browser-based WebMCP tools.

​
The problem

Some workflows should run without a human watching. Scheduled tasks. Background processing. Batch operations. You want an AI agent to do the work, but you don’t want to keep a browser open on someone’s laptop.

​
How it works

Autonomous Char combines two things: The Char Extension runs in a cloud browser service (like Browserbase). It uses Chrome’s tabs APIs to navigate pages, inject user scripts, and execute WebMCP tools against legacy portals and SaaS applications. The Tool Hub connection gives access to everything else—internal MCP servers, external MCP servers, and any other connectors configured for your org. The extension handles browser automation via WebMCP tools. The Hub routes calls to remote MCP servers—internal APIs and external services. Together, they give the agent access to the full tool surface.

​
What the extension provides

The Char Extension running in the cloud browser provides:
  • Tab management via Chrome’s tabs APIs
  • Domain allowlisting controls which sites the agent can visit
  • User script injection for WebMCP tools on legacy applications
  • Token injection for authenticating to applications (see Identity Modes)

​
What the Tool Hub provides

Through the Hub connection, Autonomous Char also has access to:
  • Internal MCP servers — your data platforms, internal APIs, custom tooling
  • External MCP servers — third-party services connected via OAuth
  • Cross-app tools — any connector registered for your org
The agent can combine browser automation with backend API calls in a single workflow.

​
Boundaries

Autonomous Char doesn’t roam freely. Browser boundaries: Domain allowlists control which sites the extension can visit. It can only navigate to configured domains. Tool boundaries: The same governance controls apply to all tool calls:
  • Connector registry determines available tools
  • Role entitlements scope access
  • Guardrails inspect content
  • Approvals gate sensitive operations
  • Audit logs everything

​
What you get

Unattended execution. Workflows run without human presence. Scheduled, triggered, or on-demand. Full tool access. Browser-based WebMCP tools plus remote MCP servers. The complete tool surface, not just browser automation. Flexible identity. Choose user-scoped for simple automation, hybrid for attributed actions, or agent identity for autonomous systems. Full governance. Every tool call—browser and backend—flows through the same controls as interactive sessions.

​
What’s in this section

Identity Modes

User-scoped, agent identity, or hybrid

​
See also

Char Extension

Browser automation component

Internal MCP Servers

Connect to internal APIs

Tool Hub

How tools are aggregated