C
CONXA
Browse docs
Docs home

Product docs

Platform OverviewClaude Automation With CONXABuild StudioConxa CloudRuntime And MCP Execution

Trust and security

Security

Legal

Privacy PolicyTerms And ConditionsCookie PolicyAcceptable Use PolicyData Processing

Billing

Billing And Refund Policy

Support

Support
Page sections
The authoring loopRecording workflow actionsReview and Human EditCompilationBuild output

Product docs

Build Studio

How builders record, edit, compile, test, and package workflows before publishing them to Conxa Cloud.

Updated June 11, 20269 min read

Summary

  • Build Studio is the local authoring environment for workflow recording and compilation.
  • Recording, auth capture, compilation, package building, and installer generation happen on the builder machine.
  • Cloud services may be contacted for login, entitlement checks, package upload, billing, telemetry, and compile-time LLM proxy calls.

The authoring loop

  1. Create a plugin with a name, target product, and starting URL.
  2. Record an authentication session when the workflow requires a signed-in target application.
  3. Record the workflow by performing the task once in the browser.
  4. Review captured steps, screenshots, inputs, and validation expectations.
  5. Compile the workflow into a skill package with selectors, intent, assertions, and recovery metadata.
  6. Test the compiled skill locally, adjust if needed, then build a plugin package or installer.

Recording workflow actions

Build Studio launches a controlled browser session and injects a capture bridge into pages and frames. The bridge records user actions such as clicks, typing, selection changes, navigation, uploads, scrolling, tabs, popups, and frame transitions.

The recorder captures more than coordinates. It keeps element signals, surrounding context, URL information, iframe chain information, timestamps, and visual references where available. This gives the compiler enough context to produce a workflow that can survive normal interface changes.

Auth capture is local

Target-site browser session files are local runtime state. They are not supposed to be included in build output and are not uploaded as part of a skill package.

Review and Human Edit

After recording, builders can inspect the workflow step by step. Human Edit is intended for practical correction: rename steps, adjust inputs, confirm screenshots, tune validation expectations, remove noise, and repair selector or semantic interpretation errors before packaging.

Deterministic edits are separate from LLM-assisted repair. Product teams can keep cleaning a workflow even when LLM-assisted pools or monthly compile credits are exhausted, depending on the plan limits enforced by the workspace.

Compilation

Compilation turns recorded events into a structured skill package. The compiler normalizes actions, removes duplicate noise, enriches events with context, selects stable element identities, creates assertions, and builds a recovery policy for the runtime.

When AI assistance is enabled, compile-time prompts may include workflow context, selected element information, screenshots, or DOM-derived signals needed to understand the workflow. The goal is to create execution metadata, not to run the customer task in the cloud.

Build output

OutputPurposeSensitive data policy
Skill packageData-only workflow artifact used by the runtime.Should not contain browser credentials or Playwright storage state.
Plugin archivePackage used for inspection, distribution, and installer assembly.Auth files are excluded from build output.
InstallerCustomer-facing executable that installs the runtime and sync configuration.Contains distribution metadata and tokens required for package sync, not target-site passwords.

Related docs

Platform Overview

How Conxa turns recorded software workflows into local MCP skills that AI tools can execute reliably.

Conxa Cloud

What the cloud dashboard and backend coordinate for published plugins, billing, teams, telemetry, and updates.

Runtime And MCP Execution

How the installed runtime exposes local browser workflow automation to Claude Desktop or another MCP client and executes skills locally.

Billing And Refund Policy

Plans, visible meters, checkout behavior, cancellations, refunds, failed payments, and enterprise billing defaults.