vmos-edge-container-api

VMOS Edge Container Management

Use this skill when you need to manage cloud phone instances through the VMOS Edge Container API.

Core Process

• Always follow Query -> Plan -> Execute -> Verify
• Base URL is http://{host_ip}:18182
• If the user has already explicitly provided host_ip, prioritize the value provided by the user
• If the user has not explicitly provided an IP, first check whether a cbs_go process exists locally; if it exists, default to host_ip=127.0.0.1
• If the user has not explicitly provided an IP, and locally there is no cbs_go, guide the user to provide host_ip
• Only accept host_ip; if the user provided cloud_ip, switch to vmos-edge-control-api
• When locally checking cbs_go , prioritize exact matching, for example pgrep -x cbs_go >/dev/null 2>&1
• For host health, check first GET /v1/heartbeat、GET /v1/systeminfo
• For the instance list, prioritize POST /container_api/v1/get_db; if the host does not support it, fall back to GET /container_api/v1/get_db or GET /container_api/v1/list_names
• For instance details, check GET /container_api/v1/get_android_detail/{db_id}
• After start-related actions, check again rom_status; for the clone process, check again clone_status
• If the current session has both installed vmos-edge-control-api, and control needs to use the host_ip route, first use get_db or get_android_detail to help it resolve the target db_id
• Most batch lifecycle interfaces use db_ids
• When creating an instance, user_name is required,bool_start is optional
• gms_start / gms_stop is a host-level operation,swap/{enable} use 1 / 0
• When uploading installation packages, files, or certificates, explicitly use multipart/form-data

Required Reading References

• First look at the index in references/api-reference.md , then open only the needed reference files by module
• Only read the corresponding module reference when precise paths, fields, polling details, or example requests are needed
• Prioritize reading relevant paragraphs on demand; do not expand the entire document into context

Security Boundaries

• Confirmation is required before host shutdown, host reset, SSD formatting, instance deletion, instance reset, one-click new device, or image upgrade
• Unless explicitly requested, do not modify IP, certificate, time zone, language, country, root permissions, or Google status