Clearer cloud setup and more reliable cleanup
Cloud account setup now explains monitoring, execution permissions, spending limits and fallback choices together. Monthly limits are clearly identified as spending allowances, not cloud credit top-ups. Account summaries use the same reported balance or metered allowance as the account detail. Nebius setup accepts a private key copied from its JSON credentials file, including escaped line breaks. DigitalOcean and Jarvis Labs are muted in the cloud picker and paused for new console connections while live verification is incomplete. Existing connections remain manageable.
If AWS monitoring connects while execution setup fails, your spending settings remain available and the console
points to the Execution section. Interrupted cloud access is recorded as CloudAccess, and unfinished machine
cleanup is retried after queue retries are exhausted. Cleanup still requires proof that the machine is gone.
Google Cloud execution on AWS Fargate supports rotating task credentials through workload identity federation. Azure GPU quota remains visible when Azure returns family names with spaces or different capitalization. When Azure verifies the subscription but cannot serve its cost query, the connection reports unavailable spend instead of an account mismatch. BYOC execution remains in Beta and is enabled per organization.
GCP and Azure execution now integrate with the cloud launcher alongside AWS. Their scoped credentials, existing networks and automatic resource cleanup are preserved. This remains a gated Beta rollout pending live verification. Cloud launches reserve enough time for machine startup, and AWS launch credentials remain valid throughout the launch window instead of expiring during setup.