Flow alpha

Closed alpha. Flow is currently invite-only.

The Builder Alpha is for creating, validating, versioning, and simulating workflow ideas with a small, supported cohort. Interest does not automatically grant access.

Current boundary

The Builder Alpha does not perform model inference, provider calls, repository or file operations, shell commands, issue actions, or other external side effects.

Separate Provider Preview

The optional Provider Preview is not part of workflow execution. Once the matching release is published and the feature is explicitly enabled for an invited account, it may list models and send one neutral, user-started request to one locally granted provider. The response is capped at 32 output tokens. It cannot execute a workflow or access repositories, files, shells, issues, or other external actions.

Login, Flow entitlement, product-specific agent pairing, and an explicit local grant for the exact provider are all required. A QA Studio configuration does not grant Flow access. When pairing is started, the hosted Flow session issues a 60-second one-time grant that is cryptographically bound to the exact local Flow pairing token. The browser keeps it in memory only; the Agent must pass an independent local license check, atomically consume the grant, and renew after the resulting session family expires within five minutes. Flow never receives the Agent license token, and the Agent never receives the Flow browser cookie. The shared agent and contract candidate are prepared, but an npm next release and a Flow consumer have not been published, so the Provider Preview and Flow workflow inference are currently unavailable.

Read known limitations before providing feedback. For general, non-confidential feedback, use the approved Flow feedback channel; use security guidance for vulnerabilities or data exposure.