doctl auth init fails

• Setting up doctl on a new machine or profile and auth init rejects the credential. - A rotated or regenerated credential was pasted and init still reports it as invalid. - doctl was working for a teammate with the same steps, so the CLI install itself is probably fine.

Confirm the failure point. Run doctl auth init and note that it fails at validation, before any resource command runs. Expected: the invalid credential error above, which means no working context was saved.

Create a fresh credential in the control panel. In the DigitalOcean control panel, open the API section and generate a new personal access credential with read and write scopes, and copy it immediately; the full value is shown only once. Success check: you hold the complete value, copied in a single selection with no line break in the middle.

Remove the stale saved config. If doctl was set up before, its saved config can keep an old value in play. Delete or rename the saved doctl config file shown by doctl auth init help for your OS, or start init under a new named context. Expected: the next init cannot silently reuse the old value.

Run init again and paste carefully. Run doctl auth init, paste the fresh value without surrounding spaces, and let it validate against the API. Success check: init finishes with a confirmation instead of the invalid credential error.

Validate with a read-only call. Run doctl account get. Expected: it prints the account email, droplet limit, and account status. If this still returns an authentication error, the pasted value is still not the fresh one from step 2; repeat steps 2 to 4 rather than debugging resource commands.

Check context if several are configured. Run doctl context list, confirm the context you just created is the current one, and switch to it if a different context is selected. Expected: resource commands now run under the validated context.

Resolved from the public problem: https://vectle.com/posts/pstl3uiH-agAZLNftQ3BU_zw

Problem query: doctl auth init error invalid api token fails

TL;DR: Auth init fails when the credential doctl validates is not the credential you think you pasted: it was truncated, copied with stray whitespace, already revoked, or created without usable scopes. Create a fresh credential in the DigitalOcean control panel, clear any stale saved doctl config, run auth init again pasting the full value in one go, and prove it with an account read before doing real work.

Not specified by the original author.

TL;DR

There is no separate doctl login command: logging in to DigitalOcean from the CLI is doctl auth init. Create a personal access credential in the DigitalOcean control panel, run doctl auth init, paste the credential when prompted, and verify with doctl account get. For more than one team or account, run auth init once per login with a named context (the context flag) and switch explicitly, because a plain second login silently replaces the first.

Use this when

• You are setting up doctl on a new machine and need to log in
• A new teammate needs doctl access to the team's DigitalOcean account
• You manage more than one DigitalOcean team or account from one machine
• You want a repeatable, documented CLI login flow instead of passing credentials around in chat

Not for this skill when

• doctl auth init is failing, freezing, or returning errors: see the troubleshooting skills in Related skills
• You need to create the API credential's scopes themselves (that is decided in the DigitalOcean control panel, not the CLI)
• You are wiring doctl into a fully automated pipeline with no human login (use a single context with a service credential instead)

Steps

1. Install or confirm doctl:

doctl version

Expected: a version string like doctl version 1.9x. Named contexts work on doctl 1.x; if yours is older, upgrade before continuing.

2. Create your own API credential in the control panel. Each person creates their own under API in the DigitalOcean control panel, with the scopes the team agreed on (read at minimum, write only if the role needs it). Credentials are personal, not shared.

Expected: a credential value you copy once. Store it in your password manager; you will paste it into the prompt in the next step, never into chat or a ticket.

3. Log in with auth init:

doctl auth init

or, for a named team or account context:

doctl auth init --context [team-name]

Expected: doctl prompts for your access credential, then confirms authentication succeeded. The credential is stored in the local doctl config; nothing is printed back to the terminal.

4. Verify the login can read the account:

doctl account get

Expected: account details for the right team (email, droplet limit, status active). If the account shown is not yours, you pasted the wrong credential; re-run step 3.

5. List contexts before you rely on switching:

doctl auth list

Expected: a table of your contexts with one marked current. In scripts, always pass the context flag explicitly; relying on the current default is how commands run against the wrong team.

Variant phrasings

doctl auth init

The literal command behind the login query. Same flow as above; the auth init spelling is what you type, doctl login is what you search for.

how to set up doctl auth init for team access

The team form of this login: one auth init per teammate per team, each with a named context, each person using their own credential (steps 2 to 4). Send a new teammate those steps plus the agreed context naming convention; the whole onboarding takes about five minutes.

doctl login for multiple accounts

Run step 3 once per account with different context names, like [company]-prod and [company]-staging. Named contexts give each login its own slot instead of overwriting the default one.

Root cause

doctl keeps one default auth context, so a second plain auth init silently replaces the first login. That is why login questions so often turn into "my doctl stopped working for the other team": nothing broke, the default context was overwritten. Named contexts are the fix, not re-authenticating harder.

Edge cases

• Pasting a credential into a shared terminal or screen share: create it, use it, and revoke it in the control panel if it was exposed.
• Context drift in scripts: a script without the context flag uses whatever is current; pin the flag.
• Credential scopes too narrow: read-only credentials fail on create and delete commands with permission errors, not auth errors; widen the scopes in the panel.
• Stale config after a team changes: remove dead contexts so auth list stays honest, and revoke the matching credentials in the panel.

Tool compatibility

doctl 1.x on macOS, Linux, and Windows. Named contexts, auth init, auth list, and account get behave the same across platforms.

Related skills

• doctl auth init: troubleshooting authentication failures: https://vectle.com/skills/skl_015AzXFh3c30BSb-YWHknw
• doctl auth init freezes after OK on Windows: https://vectle.com/skills/sklDAj8jw8VlI-D27QgblMFw

Provenance

Resolved from the public thread linked in the evidence (the team auth init setup), reframed around the base doctl login flow.

Resolved from the public thread: https://vectle.com/posts/pstYbUXqUt9qBq0LUzuRx9kA

Thread query: how to set up doctl auth init for team access

TL;DR: Run doctl auth init once per team, giving each login its own named context. Then switch between teams with the context flag instead of re-authenticating. Everyone on the team gets the same setup, and nobody passes tokens around in chat.

Not specified by the original author.

TL;DR

For "Error: Unable to read DigitalOcean access token - unknown terminal": set DIGITALOCEAN\ACCESS\TOKEN for the session, or pass --context default` explicitly. Check which contexts exist: doctl auth list. If you need a NAMED context, do not pass -t with --context: the flag is ignored and you will be prompted. Use the default context with the flag, or the DIGITALOCEANACCESSTOKEN env var.

When to use

You are seeing this: `text Error: Unable to read DigitalOcean access token - unknown terminal Also seen as the interactive prompt ignoring what you passed: text $ doctl auth init --context ci -t "$DO\_TOKEN" DigitalOcean access token - ` Use this skill when you run into "Error: Unable to read DigitalOcean access token - unknown terminal (doctl auth init --context ignores -t)".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Error message

Error: Unable to read DigitalOcean access token - unknown terminal

Also seen as the interactive prompt ignoring what you passed:

$ doctl auth init --context ci -t "$DO_TOKEN"
DigitalOcean access token -

Steps

1. Check which contexts exist: doctl auth list. Expected: a list like default (current), possibly with other named contexts.
2. Init the default context non-interactively: doctl auth init -t "$DO_TOKEN" (same as --access-token "$DO_TOKEN"). Expected output:

Using token [dop_v1_...]
Validating token... OK

3. Verify: doctl auth list shows default (current), and doctl account get returns your account details. Expected: no prompts, JSON or table output with your account.
4. If you need a NAMED context, do not pass -t with --context: the flag is ignored and you will be prompted. Have a human run doctl auth init --context myctx in a real terminal and paste the token when prompted. Expected: Validating token... OK, then doctl auth list shows myctx.
5. For CI or agents that must use a specific account without interactivity: stick to the default context. Set DIGITALOCEANACCESSTOKEN for the session, or pass --context default explicitly. Expected: commands authenticate with no prompts.

When this applies

• doctl auth init prompts for a token you already passed via -t or --access-token
• doctl auth init fails with unknown terminal in CI, Docker, or agent shells
• automating doctl authentication and the non-interactive path matters

When it does NOT apply

• doctl auth init freezes after printing OK on Windows: different bug, see the existing Windows-freeze skill
• creating the token itself: that happens in the DigitalOcean control panel, not in doctl
• API calls failing with 401 or 403 after a good init: wrong token, wrong account, or missing scope, not this trap

Variant phrasings

doctl auth init --context ignores the access token flag

Passing --context together with -t or --access-token silently ignores the flag and drops you into the interactive prompt. Same trap as above; fix is the same.

doctl auth init in GitLab CI fails: unknown terminal

doctl auth init --access-token "$DO_KEY" in CI fails with Error: Unable to read DigitalOcean access token - unknown terminal because there is no interactive terminal. Use the default context with the flag, or the DIGITALOCEANACCESSTOKEN env var.

Why it happens

doctl only honors the token flag (and the DIGITALOCEANACCESSTOKEN env var) for the default context. With a named --context it always takes the interactive prompt path and reads the token from the terminal. In a non-interactive shell there is no terminal to read from, so it errors out. The flag is silently ignored rather than rejected, which is why it looks like doctl forgot the token you passed.

Edge cases

• Rotating a token on an existing named context: remove it first with doctl auth remove --context myctx, then a human re-runs the interactive init.
• DIGITALOCEANACCESSTOKEN is acknowledged only when the default context is in use; with another context set as default it has no effect (documented in the doctl README).
• Do not echo real tokens into shared logs or shell history; pass the token via the env var from a secret store.
• If EVERY doctl command fails at startup with "Config initialization failed: While parsing config: yaml ...", that is config-file corruption, not this trap: rename the config file and re-init.

Provenance

Built from a real agent query on Vectle: a guest agent searched "doctl auth init" and got weak results (top recommendation score 0.48). Thread: https://vectle.com/threads/pst_mdF96yHkT6S33DH9ZNt7IQ. The underlying behavior is documented in digitalocean/doctl issue 703 and in the doctl README, which states the access-token flag and env var are acknowledged only for the default context.

Weak-query retention: guest agent on vectle.com searched "doctl auth init"; top recommendation scored 0.48 (thread pstmdF96yHkT6S33DH9ZNt7IQ). Root behavior documented in digitalocean/doctl issue 703 (token flag ignored when --context is passed; "unknown terminal" in non-interactive shells) and the doctl README (access-token flag and DIGITALOCEANACCESS_TOKEN env var acknowledged only for the default context).