The account gcloud has selected has no stored credentials. Run `gcloud auth login` to log that account in again, or pick a different account with `gcloud config set account`. Check `gcloud auth list` first to see which accounts actually have credentials.

```text
ERROR: (gcloud.compute.instances.list) Your current active account [[account]] does not have any valid credentials
```

## Fix

1. See what the CLI knows:
   ```bash
   gcloud auth list
   ```
   Expected: a table of accounts; the active one is marked. Missing or revoked credentials show up here.

2. Re-authenticate the account:
   ```bash
   gcloud auth login
   ```
   Expected: browser flow completes and the account appears in `gcloud auth list`.

3. Or switch to an account that already has credentials:
   ```bash
   gcloud config set account [other account]
   ```
   Expected: `gcloud config get-value account` shows the new account; commands work.

4. If the account was deleted from the machine on purpose, revoke cleanly instead:
   ```bash
   gcloud auth revoke [account]
   ```

## When this applies
- Any `gcloud` command fails with `Your current active account ... does not have any valid credentials`.
- After deleting `~/.config/gcloud/credentials.db` entries, switching machines, or a partial `gcloud auth revoke`.

## When it does NOT apply
- Application code (non-CLI) failing: that is ADC, use `gcloud auth application-default login`.
- `invalid_grant: Token has been expired or revoked`: credentials exist but the refresh token is dead; revoke and re-login.
- `You do not currently have an active account selected`: no account is selected at all; log in first.

## Compatibility
- Google Cloud SDK (gcloud) all recent versions.

## Why it happens
`gcloud auth login` stores OAuth tokens in a local credentials database keyed by account. If the entry is removed (manual cleanup, profile wipe, `gcloud auth revoke` on the wrong account) while the config still points at that account, every command fails this way. The config value and the credential store have drifted apart.

## Edge cases
- Multiple gcloud configurations (`gcloud config configurations list`): the failing command may be using a named configuration with its own account setting.
- `CLOUDSDK_ACTIVE_CONFIG_NAME` env var silently selects a configuration; check it if the active account surprises you.
- On shared machines, another user's `gcloud auth revoke` does not affect your `~/.config/gcloud`.