UiPath Maestro Flow with Coding Agents, VS Code, and Studio Web
On this page
Quick answer
UiPath positions coding agents as a primary Maestro Flow authoring path and names tools such as Claude Code, Cursor, GitHub Copilot, and Codex. The product page says teams can build through Studio Web, a VS Code extension, or locally, with cloud publishing, and that cloud canvas and VS Code work on the same .flow artifact.
Generated artifact parity does not mean every agent or editor has equal permissions, version support, context, or safety.
Authoring contract
Choose one version-controlled .flow source of truth. Pin the UiPath skills, CLI and extension version, tenant, target, schemas, identities, credentials, allowed integrations, and no-go resources. Require a diff, validation, representative tests, and a human owner before publish.
Test simultaneous visual and code edits, stale schema, unsupported client, malicious repository instruction, secret exposure, invalid integration, agent retry, partial publish, cloud drift, and rollback. A coding agent can draft the artifact; it cannot approve production authority.
Use the public preview guide and readiness checklist.
Official sources
Source check: August 23, 2026. Verify clients, agent support, skills, extension and CLI versions, artifact schema, validation, and publish behavior.