What problem does it solve? Deploying an Internet Computer project to a user-owned cloud engine requires linking the icp CLI to the engine console identity, targeting the correct subnet, and handling sandboxed environments where browser sign-in cannot reach the CLI — steps that fail silently or with authorization errors when done wrong. ## Core Features & Use Cases - Identity Linking: Link the icp CLI to the engine console identity with icp identity link web, including a delegation handoff flow for remote sandboxes where the browser cannot reach the CLI's 127.0.0.1 callback. - Subnet-Targeted Deploy: Run icp deploy -e ic --subnet <subnet-id> against the engine's subnet, with guidance on obtaining the subnet id from the console. - Console App Metadata: Tag canisters with __META_* environment variables so the console groups them into a named app with labels, an icon, and an Open button, plus bake version metadata (service:git:sha, service:version) into the wasm. - Cross-Subnet Proxy: Route cycle-bearing cross-subnet calls (exchange-rate canister, threshold ECDSA/Schnorr, vetKD) through a funded proxy canister, since CloudEngine subnets forbid them directly. - Use Case: An agent in a cloud sandbox needs to ship a user's built IC project to their OpenCloud engine — it creates a delegation request, the user signs it locally, and the agent deploys with proper app naming and version metadata. ## Quick Start Ask the assistant to deploy your built Internet Computer project to your cloud engine, providing your engine's subnet id from the console's App Center page.
