---
title: Why is Vercel CLI asking me to log in?
description: Information on why you may be getting prompted to log in to Vercel CLI.
url: "https://vercel.com/kb/guide/why-is-vercel-cli-asking-me-to-log-in"
published: 2025-11-03
last_updated: 2025-11-10
authors: Allen Hai
install_vercel_plugin: npx plugins add vercel/vercel-plugin
---

You might have spent some time away from using [Vercel CLI](https://vercel.com/docs/cli#getting-started) only to return to it providing you with the following error:

```text
Error! The specified token is not valid
```

This article covers off the likely reason for this and the action required to ensure Vercel CLI works again as it did previously.

## Vercel Token Expired

Vercel CLI requires users to log in and authenticate before accessing user specific content or performing administrative tasks such as deleting projects or adding secrets. After logging in, a new token is generated which gives full permission to interact with the account.

> **WARNING:** If there has been no activity using the token for **10 days**, the token is deemed inactive and expires as a result.

Tokens are expired to increase the security of the Vercel platform platform by making sure there aren't any tokens issued that can be abused in the future.

## Issuing a New Token

If you are using Vercel CLI locally, use the following command:

```bash
vercel login
```

By using the `vercel login` [command](https://vercel.com/docs/cli#commands/login), you will be logged in to your Vercel account locally, creating a token that will then be used for all other [Vercel CLI commands](https://vercel.com/docs/cli#commands).

If you are using Vercel CLI in a CI/CD environment, visit the [tokens page](https://vercel.com/account/tokens) on the Vercel Dashboard and create a new token that can replace the one previously invalidated.

If you'd like to keep the token active, make sure to use the CLI at least once every 10 days.

## Related Documentation

- [Vercel CLI](https://vercel.com/docs/cli)

## More Vercel CLI guides

- [How can I run end-to-end tests after my Vercel Preview Deployment?](/kb/guide/how-can-i-run-end-to-end-tests-after-my-vercel-preview-deployment): Learn how to use the Vercel CLI in combination with your CI/CD provider to run end-to-end tests for every code change.
- [The Complete Guide to Vercel Connect](/kb/guide/vercel-connect): Use Vercel Connect to call provider APIs like Slack, GitHub, Linear, Microsoft, Discord, Snowflake, and Salesforce from your agents and services with short-lived, scoped tokens instead of long-lived secrets.
- [Does Vercel support Docker deployments?](/kb/guide/does-vercel-support-docker-deployments): Vercel supports deploying OCI-compatible container images through Vercel Functions and Vercel Container Registry, with Active CPU pricing and automatic scaling.

## Reference Architecture

Choose a stack and work through the decisions behind it, with curated documentation, guides, templates, and courses to help you build.

- [Agent stack](/kb/architecture/agents): Build and operate agents with models, tools, and durable workflows.
- [Web applications](/kb/architecture/web): Choose rendering, data, authentication, and caching approaches.
- [Backends](/kb/architecture/backends): Choose a runtime, connect services, and run background work.

[Browse all stacks](/kb/architecture)

## Build with prompts

Build an app, extend an agent, or improve your project with ready-to-use prompts for your coding agent.

[Browse the prompt library](/kb/prompts) · [Read the Markdown index](/kb/prompts.md)