for_cloud_device() SDK integration still exists for authorized MaaS cloud-device access.
Local mobile-use, the Minitap API, BrowserStack, and Minitap cloud devices remain supported through their current public flows.
A Minitap API key does not restore hosted tasks, profiles, or dashboards. The
minitap LLM provider and for_cloud_device() use separate retained MaaS APIs; access depends on your account and credentials.Replace hosted tasks and profiles
Move the task prompt into code and load anAgentProfile from a local configuration file:
.env
Move custom model configurations to OpenRouter
Recreate custom hosted model profiles locally with an OpenRouter API key and model identifier. OpenRouter provides one supported endpoint for the model catalog that was previously configured in Platform:.env
LLM in your local AgentProfile for the planner, orchestrator, cortex, or executor role that used the hosted custom model.
Replace hosted cloud devices
Choose the device path that matches your environment:- Connect an Android device or emulator through ADB.
- Connect an iOS simulator or physical device using the documented local setup.
- Use BrowserStack for supported remote iOS devices.
- Connect a Minitap cloud device through the supported mobile-use CLI flow with
MAAS_API_URL, a tenant-scopedMAAS_TENANT_API_KEY, and your tenant ID:
PlatformTaskRequest or for_cloud_mobile(). They belong to the removed hosted task flow. for_cloud_device() is a separate SDK integration and is not a replacement for hosted tasks.
Install apps on Minitap cloud devices
The supported cloud-device flow accepts HTTPS artifact URLs or local.ipa and .app files for iOS installs:

