The console names and groups apps from variables their canisters carry; a canister deployed without them is listed as an app of its own, named by its canister id.
- Set these canister environment variables on the app's canisters, for example in your project's
icp.yaml:
__META_PROJECT: the app's name. Give every canister of the app the same value; canisters that share it are listed as one app.__META_NAME: each canister's own label, like Frontend or Backend.__META_MAIN_CANISTER:trueon the one canister the app opens at, usually the frontend.- Optional, on that main canister:
__META_BASE_URL(an https address the Open button uses) and__META_ICON_PATH(the icon's path under it, like/favicon.svg).
- Deploy the canisters again.
- Reload Your apps and services: the canisters show as one app, under its name.
Good to know
- Easiest: ask your coding agent. The deploy-to-cloud-engine skill that the Build with agents prompt installs knows these variables.
- To see what a canister carries, open its page and look under Environment, App metadata.
- A canister with a
__META_NAMEbut no__META_PROJECTis listed alone, under that name. - One app split over several rows usually means its canisters carry different
__META_PROJECTvalues. - Apps installed with Upload a bundle are named after the bundle, and Caffeine and OpenSaaS apps name themselves.
- The variables only change how the console lists the app; your app's code doesn't read them.