Features
-
Workflow browser launch metadata: Workflows can now declare
startUrl,gpu, andviewportin their definition options. These properties are exposed onLibrettoWorkflowandExportedLibrettoWorkflow, preserved through hosted deploy discovery, and passed through generated workflow proxies — enabling Libretto Cloud to configure the browser environment for deployed workflows. -
Headless mode for providers:
libretto run --provider <name> --headlessandlibretto open --provider <name> --headlessnow thread the headless flag through to the provider browser session request. The Libretto Cloud and Kernel providers both forwardheadlessto their respective session-creation APIs. Previously, provider runs always defaulted to headless; now--headless/--headedcontrol the mode just as they do for local runs. -
Headless/headed flags for cloud job creation:
libretto cloud jobs createnow accepts--headlessand--headedflags. When either is supplied, theheadlessfield is sent to the cloud job creation API. -
Libretto Cloud website auth: The Libretto website now hosts full sign-in, sign-up, workspace onboarding, invite acceptance, and email verification flows.
libretto cloud auth loginandlibretto cloud auth signupnow open a browser to the hosted sign-in page and wait for browser-side approval, instead of prompting for credentials in the terminal. Invite acceptance is handled through a website link rather than a CLI sub-command. -
Cloud dashboard: A new dashboard page on the Libretto website lets signed-in users view hosted jobs, browser sessions, team members, and billing. Owners can invite users, update member roles, remove members, and open the billing portal. Users can delete their own account from the dashboard.
Improvements
-
Cloud user ID in telemetry: When signed in to Libretto Cloud, the CLI now includes the configured cloud user ID as an optional
cloudUserIdfield in telemetry payloads. The telemetry disclosure text has been updated accordingly. No emails, cookies, or API keys are sent. -
Auth profile guidance: Documentation and agent skill files now clarify that auth profiles are browser-runtime-specific — local profile files are not available to provider browsers, and profiles must be revalidated when switching providers. Guidance for deploying authenticated workflows with hosted provider browsers has been expanded.
-
Run mode documentation: Agent skill files now document the three workflow run modes (local browser, hosted browser with
--provider, deployed workflow) and when to set a default provider in.libretto/config.json.