Browse docs
Product docs
Runtime And MCP Execution
How the installed runtime exposes local browser workflow automation to Claude Desktop or another MCP client and executes skills locally.
Summary
- The runtime is a local MCP server installed on the customer machine.
- It syncs data-only skill packages, launches browser automation locally, and reports compact telemetry.
- Runtime browser sessions and target-application credentials are stored locally and are not part of published skill packages.
Local MCP server
The runtime installs on the end user machine and registers as an MCP server. MCP clients can list available skills, request input schemas, execute a skill, inspect execution status, cancel execution, refresh skill packages, and read skill metadata where permitted.
Because it runs locally, the runtime can operate the user browser session without sending the live UI state to a remote execution service.
Skill sync
The runtime checks Conxa Cloud for skill package updates and downloads package deltas or current package content as configured. Files are verified and written atomically so a failed update does not leave a half-written package in place.
The sync token packaged for a company should be treated as distribution-sensitive. It allows the runtime to retrieve data-only skill packages for that company, but it is not the same thing as the end user target-site session.
Execution loop
- The MCP client asks the runtime to execute a named skill with validated inputs.
- The runtime loads the skill package and starts or reuses a browser context.
- Each workflow step resolves its target element using compiled selectors, accessibility signals, visual context, and recovery policy as needed.
- Assertions verify that the step produced the expected state.
- Telemetry is batched and sent to Conxa Cloud so builders can see health and failure trends.
Recovery behavior
Conxa skills are designed to recover from routine UI drift. The runtime starts with deterministic recovery paths and only escalates to more expensive repair strategies where the compiled policy allows it.
Some steps are intentionally not recoverable. Frame-enter and frame-exit markers, for example, describe navigation boundaries and should not be treated as interactable elements.
Runtime storage
| Data | Typical location | Purpose |
|---|---|---|
| Skill packages | Local Conxa skill-pack directory | Defines available MCP tools and execution steps. |
| Runtime token | OS keychain where supported | Authenticates package sync for the installed company runtime. |
| Browser session | Local encrypted runtime cache | Keeps target-site session state on the customer machine. |
| Execution logs | Local runtime logs and cloud telemetry summary | Supports debugging and operational health checks. |
Related docs
Claude Automation With CONXA
How Conxa packages browser workflow automation as local MCP skills that Claude Desktop can invoke safely.
Platform Overview
How Conxa turns recorded software workflows into local MCP skills that AI tools can execute reliably.
Security
Security boundaries, local execution guarantees, auth handling, token storage, and practical operational limits.
Privacy Policy
How CONXA collects, uses, stores, shares, and protects information across the website, dashboard, Build Studio, cloud services, and runtime telemetry.