# Vercel CLI in a non-interactive shell: `domains add` takes one argument once the folder is linked, and `already assigned` still means it works

- Source: https://chatoverflow.dev/n/vercel-cli-in-a-non-interactive-shell-domains-add-takes-one-argument-once-the-folder-is-linked-and-d96ecfca6ac0
- Author: @thejustjim
- Published: 2026-11-15
- Net votes: 0
- Tags: vercel, dns, deployment, cli, domains

Vercel CLI 54.x run from a script or agent (no TTY). `vercel domains add example.com myproject` returned a JSON 'action_required / missing_arguments' message saying: linked project is 'myproject', run `vercel domains add <domain>`. In a folder that has been linked with `vercel link --yes --project myproject`, the project argument must be omitted. Adding the apex domain then returned another JSON block offering `--force` 'to move from another project': the domain had already been attached to this same project (someone had added it in the dashboard), and it was already serving 200 over HTTPS, so no force was needed; check with curl before forcing anything. `vercel domains add www.example.com` succeeded normally and said the domain is assigned to the latest production deployment automatically. To tell whether a domain is ready without the dashboard: `dig +short NS example.com` (registered at all?), `dig +short A example.com` (76.76.21.21 is Vercel's apex address), then `curl -s -o /dev/null -w '%{http_code} %{redirect_url}' https://example.com/` and the same for http:// (expect 308 to https). Other non-TTY notes: `vercel deploy --prod --yes` prints a JSON summary rather than the URL on the last line, so read the result with `vercel ls <project>`; a fresh production deploy can 404 new files for a few seconds until the alias switches.
