Use Ollama Cloud models
Ollama Cloud models run on Ollama’s hosted infrastructure while you keep using the local Ollama API at http://localhost:11434. You do not need a separate provider, base URL, or API key in Ollama Client.
Set up Ollama Cloud
Section titled “Set up Ollama Cloud”-
Install or update Ollama.
-
Sign in through the Ollama app, or run:
Terminal window ollama signin -
Confirm that a cloud model works through Ollama itself:
Terminal window ollama run minimax-m3:cloud -
Open Ollama Client and refresh the model menu.
-
Select a model carrying the Cloud badge and start chatting.
The model is served through your normal Ollama provider. Nothing large is downloaded to your computer.
Automatic discovery
Section titled “Automatic discovery”Recent Ollama versions expose hosted recommendations through the local daemon. Ollama Client combines those :cloud recommendations with the locally installed models returned by /api/tags, so both appear in the same model menu.
The Cloud badge shows the required plan when Ollama reports one. Hover it to see Ollama’s model description. The response is cached briefly to avoid repeatedly polling the experimental endpoint.
Older Ollama versions may not provide cloud recommendations. That does not break local discovery: Ollama Client silently keeps the ordinary local model list.
If a cloud model does not appear
Section titled “If a cloud model does not appear”First update Ollama and make sure you are signed in. Then verify the model in a terminal:
ollama run minimax-m3:cloudIf the model works there but is still absent from Ollama Client:
- Open Settings → Providers → Ollama.
- Add the exact model name, such as
minimax-m3:cloud, under Model IDs. - Refresh the model menu and select it.
This manual entry is only a compatibility fallback. It does not download or delete a model.
Output-token setting
Section titled “Output-token setting”Leave Maximum Tokens on Auto (recommended). Ollama Client omits the wire-level output limit in Auto mode so the daemon can choose a valid value for either a local or hosted model.
Older releases sent their internal -1 sentinel to Ollama. Some cloud models reject that value with HTTP 400. You should no longer need to replace it with a large positive number manually.
Troubleshooting
Section titled “Troubleshooting”HTTP 401 or sign-in error
Section titled “HTTP 401 or sign-in error”Open the Ollama app or run ollama signin, then retry the same model with ollama run <model>:cloud.
HTTP 400 while generating
Section titled “HTTP 400 while generating”Reset Maximum Tokens to Auto. Also start a new text-only chat if the selected cloud model does not support images or other input from the current conversation.
Model requires another plan
Section titled “Model requires another plan”The Cloud badge may include free, pro, or another plan reported by Ollama. Availability and usage limits are controlled by your Ollama account. See Ollama Cloud for current account and usage details.
Local models work but cloud models do not
Section titled “Local models work but cloud models do not”That confirms the local daemon is reachable, but not that it is authenticated for cloud inference. Test the exact :cloud model with the Ollama CLI; its error is usually the clearest sign-in or plan diagnostic.