Script tag or NPM package

A script tag is the fastest evaluation path. It lets a product team test natural-language control on a staging page and identify the workflow that creates measurable value.

The NPM path is better for production because it fits typed builds, release review, version pinning, and feature flags. Teams can keep model routing, telemetry, and safety policy under normal frontend governance.

• Use script-tag trials for speed and stakeholder demos.
• Use NPM integration for production release control.
• Keep the agent behind feature flags until prompts and actions are stable.
• Instrument prompt, action, checkout, and completion events from day one.

DOM-based control changes the cost model

A page-level agent can use text, labels, buttons, forms, and accessible structure rather than relying only on screenshots. That can make common tasks faster, cheaper, and easier to inspect.

The tradeoff is responsibility. Your app should have reliable labels, predictable state, clear disabled controls, and a policy for actions that require confirmation.

A good first workflow

Pick a workflow where the user knows the desired outcome but hates the steps: updating settings, filling a structured form, creating a report, triaging a support case, or navigating a dense admin console.

Avoid a first launch that tries to control the whole product. Pro annual works best when the first paid scope is concrete and measurable.

Common questions