Set up with an AI coding assistant

​

The prompt

I'm setting up a PolyAI account and an API key for the PolyAI APIs using
PolyAI's CLI (the polyai-adk package on PyPI, source at github.com/polyai/adk,
docs at https://docs.poly.ai/adk/get-started/agentic-setup). Please walk me
through it.

Before running anything, summarise the plan in three lines and wait for my "go".
The last step writes POLY_API_KEY to my shell profile (or user environment on
Windows), so include that in the summary.

1. Check for uv with `uv --version`. If it's missing, ask me how I'd like to
   install it: `brew install uv` on macOS, `winget install astral-sh.uv` on
   Windows, or `pipx install uv` anywhere. Don't pipe a script into a shell.
2. Install the CLI: `uv tool install --python 3.14 polyai-adk`. Then run `which -a poly`
   (PowerShell: `Get-Command poly -All`). If the first `poly` listed isn't the one uv
   installed, run every `poly` command below as `uvx --from polyai-adk poly ...` and tell
   me why. If `poly` isn't found at all, run `uv tool update-shell` and tell me to open a
   new terminal.
3. Run `poly apikey --region studio`. It prints a sign-in URL and opens it if it
   can. Show me the URL either way; I'll sign in with GitHub in my browser. Allow
   up to five minutes, since it waits for me.
   If it reports "Multiple accounts found", show me the list, ask me which one to use,
   and re-run with `--account-id <id>`. I won't need to sign in again.
4. Show me the summary it prints. It only prints a masked key. Don't read
   ~/.poly/credentials.json, the registry, or my shell profile to see the key.
5. Verify with `poly project list --region studio` and tell me what it shows.
   Remind me to open a new terminal so POLY_API_KEY is available.

If any other step fails, show me the output and stop. Don't retry with other flags.

​

What the assistant will do

1. Check for uv and ask how you’d like to install it if it’s missing.
2. Install the CLI with uv tool install --python 3.14 polyai-adk and check which poly runs. If an older one comes first on your PATH, it runs the new one with uvx --from polyai-adk poly instead.
3. Run poly apikey --region studio and show you the sign-in URL.
4. Wait while you approve the sign-in in your browser with GitHub.
5. If you belong to more than one account, show you the list, ask which to use, and re-run with --account-id.
6. Show you the masked summary once it completes.
7. Verify the key with poly project list --region studio.

​

What gets written where

• The API key, to ~/.poly/credentials.json (mode 600) under the studio region — every poly command reads this.
• POLY_API_KEY, to your shell profile (~/.zshrc, ~/.bash_profile, ~/.bashrc, or your fish config) — for the PolyAI SDKs and other tools that read it directly.
• On Windows, POLY_API_KEY goes into your user environment variables instead of a profile file.

​

Requirements

• Python — handled by uv, which downloads 3.14 if you don’t already have it.
• uv itself — brew install uv, winget install astral-sh.uv, or pipx install uv.
• A GitHub account.
• An AI coding assistant that can run shell commands — Claude Code, Cursor, Codex, and Copilot CLI all qualify. This prompt has been tested with Claude Code.

​

If something goes wrong

• poly not found after install — run uv tool update-shell and open a new terminal.
• poly apikey not recognised — an older poly comes earlier on your PATH. which -a poly (PowerShell: Get-Command poly -All) lists them in order. Run uvx --from polyai-adk poly apikey --region studio, or remove the older install.
• “Multiple accounts found” — pick one from the list and re-run with --account-id <id>. You won’t sign in again. Run it yourself in a terminal to pick from a list instead.
• POLY_API_KEY already set to a different value — the command stops with exit code 2; the assistant will ask you before rerunning with --force.

​

Telemetry