How do I fix "Model not found" in Atlas?

Run `atlas models` and copy the exact provider/model id from the list, then fix the `model` value in atlas.json or through the /models picker. Provider.getModel raises ProviderModelNotFoundError for any pair not in the resolved catalog.

How do I list available models in Atlas?

Run `atlas models`. It prints the resolved catalog that Provider.getModel checks against, which is the authoritative source for valid provider/model ids.

What format does the model value in atlas.json use?

The provider/model format, both halves present and separated by a slash. Atlas prints "Or check your config (atlas.json) provider/model names" when the pair is not found in the resolved catalog.

What does the Did you mean line mean in an Atlas model error?

ProviderModelNotFoundError carries a `suggestions` field, so a Did you mean line means Atlas found a close fuzzy match in the resolved catalog. Read it before guessing, since it usually holds the correct id.

Atlas shows my provider but not my model, why?

The model id is not in the resolved catalog for your account. Confirm your account actually has access to that model id, or pick a different one from `atlas models`. No atlas.json edit can add a model to the catalog.

Can I change the Atlas model without editing atlas.json?

Yes. Use the /models picker in the Atlas TUI. It writes the same value and cannot produce an id outside the resolved catalog, which removes the typo failure mode. Atlas also lets you switch model and provider on the fly with favorites and recents.

Why did Atlas start failing with Model not found when nothing changed?

A provider can retire a model id, which removes it from the resolved catalog even though atlas.json never changed. Run `atlas models`, copy a current provider/model id, and update the `model` value.

Atlas error: Model not found: <provider>/<model>

Atlas exits with "Model not found: <provider>/<model>" because Provider.getModel raises ProviderModelNotFoundError when the providerID/modelID pair is not in the resolved catalog, and both the CLI and the TUI format that tagged error into a multi-line hint. Fix it by running `atlas models` to list available models, copying the exact provider/model id from that list, and correcting the `model` value in atlas.json or through the /models picker.

Why does Atlas say Model not found

Atlas says "Model not found: <provider>/<model>" because Provider.getModel raises ProviderModelNotFoundError when the pair you asked for is absent from the resolved catalog, and both of its 2 halves, providerID and modelID, must match. The Atlas CLI and the TUI format that tagged error into the multi-line hint you see on exit.

Two halves of the identifier can be wrong, and Atlas names both in the error. A wrong providerID means Atlas has no such provider in its resolved catalog at all. A wrong modelID means the provider exists but does not carry that model id. The multi-line hint points at the same two places every time: Try: `atlas models` to list available models, and Or check your config (atlas.json) provider/model names. Atlas lets you switch the active model and provider on the fly with favorites and recents, so a stale favorite pointing at a retired model id is a common way to arrive here.

How to fix Model not found in Atlas

Fix the Atlas "Model not found" error in 4 steps: run `atlas models` and copy the exact provider/model id from the list, fix the `model` value in atlas.json or through the /models picker, confirm your account has access to the model id, then re-run and read the Did you mean line before guessing.

`atlas models` is the authoritative list, because it prints the resolved catalog that Provider.getModel checks against. Copy the id from there rather than from documentation, a blog post, or memory. The `model` value must use the provider/model format, both halves present and separated by a slash. If you prefer not to hand-edit atlas.json, the /models picker in the Atlas TUI writes the same value for you and cannot produce an id that is not in the catalog, which removes the typo failure mode entirely.

What the Did you mean suggestions in Atlas tell you

ProviderModelNotFoundError in Atlas carries a `suggestions` field, which is why the error sometimes prints a Did you mean line. Step 4 of the documented fix is to read that line before guessing, because the suggestions are fuzzy matches drawn from the resolved catalog and the correct id is usually very close to what you typed.

Read the Did you mean line before guessing at another id, because it usually contains the exact answer. A suggestion appearing at all means the catalog holds something close to your input, which almost always indicates a typo, an outdated model id, or a version suffix that has moved. When no Did you mean line prints, the opposite is true: Atlas found nothing resembling your input, which points at a wrong providerID rather than a mistyped model. Run `atlas models` in that case and read the provider names first.

Fixing the model value in atlas.json

Fixing the `model` value in atlas.json is step 2 of the documented fix for Model not found in Atlas. The value must use the provider/model format, and both halves have to match ids in the resolved catalog, which is what the "Or check your config (atlas.json) provider/model names" hint is pointing at.

Edit atlas.json with the id copied verbatim from `atlas models`. Slashes, hyphens, and version suffixes are all load bearing and none of them are forgiving. A config that was correct months ago can break when a provider retires a model id, and the error will point at atlas.json even though nothing in your file changed. Atlas snapshots file changes as git patches, so if Atlas edits config on your behalf you can diff and roll back the change. The /models picker is the alternative to hand-editing, and it cannot write an id outside the catalog.

When the provider is right but the model is missing in Atlas

Step 3 of the documented fix applies when `atlas models` lists the provider but not your model id: confirm your account actually has access to that model. Provider.getModel raises ProviderModelNotFoundError for any providerID/modelID pair missing from the resolved catalog, and access-gated models do not appear there for accounts without entitlement.

This is the case where the Atlas config is not the problem. The provider resolved, the id is plausible, and the model is simply not available to you. No edit to atlas.json can add a model to the resolved catalog, and re-running Atlas will keep raising ProviderModelNotFoundError. The honest fix lives with the provider: gain access to the model id, or pick a different one from `atlas models` and set that in atlas.json instead. Atlas lets you switch the active model and provider on the fly with favorites and recents, so trying an available model costs very little.

How to fix it

01Run `atlas models` and copy the exact provider/model id from the list.
02Fix the `model` value in atlas.json (or the /models picker) to use the provider/model format.
03If the provider is right but the model is missing, confirm your account actually has access to that model id.
04Re-run; ProviderModelNotFoundError carries `suggestions`, so read the Did you mean line before guessing.

Frequently asked questions

How do I fix "Model not found" in Atlas?: Run `atlas models` and copy the exact provider/model id from the list, then fix the `model` value in atlas.json or through the /models picker. Provider.getModel raises ProviderModelNotFoundError for any pair not in the resolved catalog.
How do I list available models in Atlas?: Run `atlas models`. It prints the resolved catalog that Provider.getModel checks against, which is the authoritative source for valid provider/model ids.
What format does the model value in atlas.json use?: The provider/model format, both halves present and separated by a slash. Atlas prints "Or check your config (atlas.json) provider/model names" when the pair is not found in the resolved catalog.
What does the Did you mean line mean in an Atlas model error?: ProviderModelNotFoundError carries a `suggestions` field, so a Did you mean line means Atlas found a close fuzzy match in the resolved catalog. Read it before guessing, since it usually holds the correct id.
Atlas shows my provider but not my model, why?: The model id is not in the resolved catalog for your account. Confirm your account actually has access to that model id, or pick a different one from `atlas models`. No atlas.json edit can add a model to the catalog.
Can I change the Atlas model without editing atlas.json?: Yes. Use the /models picker in the Atlas TUI. It writes the same value and cannot produce an id outside the resolved catalog, which removes the typo failure mode. Atlas also lets you switch model and provider on the fly with favorites and recents.
Why did Atlas start failing with Model not found when nothing changed?: A provider can retire a model id, which removes it from the resolved catalog even though atlas.json never changed. Run `atlas models`, copy a current provider/model id, and update the `model` value.

Try Atlas in your terminal

The terminal-native AI coding agent. Free core, single binary.

Install Atlas

Related guides

Atlas with GPT-4.1 mini (2026): The Cheap Slot That Still Holds a Million Tokens

GPT-4.1 mini gives Atlas a 1,047,576 token context at $0.40 per Mtok input and $1.60 per Mtok output. The right small_model when your cheap slot needs a huge window.

Atlas with GPT-5 Nano: The Cheapest Model in the OpenAI Registry in 2026

GPT-5 Nano in Atlas: $0.05 per Mtok input and $0.40 per Mtok output, the cheapest model in the OpenAI registry, and the right pick for the small_model slot.

Atlas with Mistral Large 2.1 (2411): A 2026 Setup Guide

Mistral Large 2.1 (2411) runs Atlas on EU infrastructure with a 131,072 token context at $2.00 / 1M input tokens and $6.00 / 1M output tokens. Setup and honest limits.

Atlas for SolidJS: A Terminal-Native AI Coding Agent Built on Solid, for Solid, in 2026

Atlas is a terminal-native AI coding agent for SolidJS in 2026. It reads your createSignal and createMemo graph, fixes destructured props that break reactivity, and runs vitest.

Atlas for Rust in 2026

Adopt Atlas, the terminal-native AI coding agent, for Rust development in 2026. Tackle borrow checker errors and clippy lints with Atlas's secure, approval-gated assistance.

Atlas for C in 2026

Atlas is a terminal-native AI coding agent for C in 2026. Run it in a project with a Makefile, have it find memory leaks or add Unity tests, and review the diff.

Atlas vs. Goose: Choosing Your AI Coding Agent in 2026

Compare Atlas and Goose for 2026. Atlas offers terminal-native TUI and code-specialized features. Goose provides shareable Recipes and 70+ MCP extensions for general agentic workflows.

Atlas with Qwen Turbo: The $0.05 per Mtok Small Model Slot in 2026

Run Atlas on Qwen Turbo in 2026. Alibaba's cheapest reasoning tier gives 1M tokens (1,000,000) of context at $0.05 per Mtok input, $0.20 per Mtok output.

Browse this resource hub