## TL;DR
"Project not found" from the Doppler CLI means the CLI is looking in the wrong workplace, the project name is misspelled, or the service token is scoped to a different project. Verify the workplace, list the projects you can see, and re-run `doppler setup`. The project resolves once all three agree.

## Error
```text
doppler: project not found in cli
```

## Steps
1. Check the configured workplace: run `doppler configure get workplace` and compare it with the workplace shown in the dashboard URL. Expected: they match; if not, that is the problem.
2. List what the CLI can actually see: run `doppler projects` and look for your project name spelled exactly. Expected: either you spot a typo or you confirm the project is genuinely invisible to this identity.
3. Check the token scope: if you authenticate with a service token, verify in the dashboard which project and config it is scoped to. Expected: the token scope matches the project you want.
4. Re-run `doppler setup` in the project directory and select the correct workplace, project, and config interactively. Expected: the CLI writes the correct scope to `.doppler.yaml`.
5. Retry your original command (for example `doppler secrets` or `doppler run --`). Expected: the project resolves and secrets are accessible.

## When to use
- Doppler CLI reports project not found while the dashboard shows it
- Switching workplaces, projects, or service tokens
- CI jobs that worked with one token and broke with another

## When not to use
- Secrets resolve but values are stale (sync issue)
- Permission denied on a visible project (access, not naming)

## Tool compatibility
- Doppler CLI (`doppler setup`, `doppler projects`, `doppler configure`); service tokens

## Variant phrasings
### doppler setup cannot see my project
The CLI authenticates to one workplace at a time; switch the workplace or use a token scoped to the right one.

### doppler project not found in ci
Service tokens are scoped to a single project and config; generate the token from the project you actually want.

## Why it happens
Doppler scopes everything (projects, configs, tokens) to a workplace, and the CLI caches one scope per directory. A stale `.doppler.yaml`, a personal token from the wrong workplace, or a service token minted for project A while you ask for project B all produce the same "not found".

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_3o106LMIBgVG6FKEp37-JA