Build and deploy

Link the icp CLI to your console sign-in

All help topics

icp identity link web signs the icp CLI in as you, with the same identity that administers your engines; when it opens the console's Link your CLI page, you confirm there and sign in.

  1. Run the link command in your terminal. The Connect your ICP CLI dialog shows it for your console (on opencloud.org: icp identity link web opencloud --app opencloud.org). Coding agents usually run icp identity link web <name> --auth followed by the console's address.
  2. Your browser opens a sign-in. With --auth it is the console's Link your CLI page; with --app, Internet Identity opens directly.
  3. On Link your CLI, read the warning: it names the program on your computer that asks to act as you on your engines. Continue only if you started the command yourself, in your terminal, just now.
  4. Tick I started this in my terminal just now.
  5. Click Continue, or one of the sign-in buttons under or, and sign in with the same identity you use for the console.
  6. When the page says CLI linked, close the tab and go back to your terminal.
Good to know
  • A link made on Link your CLI lasts an hour. When it runs out, icp identity reauth <name> signs the CLI in again; the link command itself refuses a name the CLI already has.
  • Linking failed: go back to your terminal and run the command again.
  • Invalid request: the page was opened without the CLI's request, for example from a bookmark. Start from your terminal.
  • The page only ever hands the sign-in to a program on your own computer, never to a website.
  • The CLI must run on the computer whose browser you sign in with. From a cloud sandbox the sign-in can't complete; agents there use the ICP MCP connector instead.
  • Signing in with a different identity than your console's gives the CLI a different principal, and your engine refuses its deploys.

More about the same page

Still stuck? Contact support