Skip to content

Known limitations of the Flow alpha ​

Closed alpha. These limits are intentional in the current Builder Alpha.

Included ​

  • Workflow design, validation, versioning, and simulation.
  • Reviewable workflow ideas without a live execution claim.
  • A prepared, separately gated Provider Preview contract; after release it may list models and send one explicit neutral request capped at 32 output tokens.

Not included ​

  • Model inference or provider calls from a workflow.
  • Repository, file, shell, or issue operations.
  • External actions, unattended execution, or general availability.
  • A published Flow consumer or npm next release for the prepared shared agent/contract candidate.

The Provider Preview is not currently available. When released, it will remain invite-only, separate from workflow execution, and dependent on login, entitlement, product-specific pairing, and a local grant for the exact provider. It does not make workflow inference available.

The prepared pairing authorization is deliberately short-lived: its challenge-bound browser grant expires after 60 seconds and the resulting local Flow session family after at most five minutes. Reauthorization is expected; there is no unattended or long-lived Flow Agent session in this Alpha contract.

Please keep production data, customer material, secrets, and confidential workflow contents out of alpha feedback. Follow the Flow changelog for public changes.

QA Studio · Flow · Shared local agent · Provider readiness