github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-23 06:01:37 -05:00
Code Issues 16.9k Packages Projects Releases 122 Wiki Activity

[PR #14057] [MERGED] cmd: helpful error message for remote models #45737

New Issue
Closed
opened 2026-04-25 01:23:37 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-25 01:23:37 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/ollama/ollama/pull/14057
Author: @BruceMacD
Created: 2/3/2026
Status: ✅ Merged
Merged: 2/4/2026
Merged by: @BruceMacD

Base: main ← Head: brucemacd/chat-cloud-signin

📝 Commits (2)

  • f45f2fa cmd: helpful error message for remote models
  • 7b32333 move cloud check before first log

📊 Changes

2 files changed (+113 additions, -1 deletions)

View changed files

📝 cmd/cmd.go (+12 -1)
📝 cmd/cmd_test.go (+101 -0)

📄 Description

When trying to use cloud model with OLLAMA_HOST="ollama.com" while not signed in, a helpful error message is displayed. This should be the same experience for models which specify a remote instance.

Before:

❯ OLLAMA_HOST=ollama.com ollama run deepseek-v3.1:671b
You need to be signed in to Ollama to run Cloud models.

❯ ollama run deepseek-v3.1:671b-cloud
Connecting to 'deepseek-v3.1:671b' on 'ollama.com' ⚡
>>> hi
Error: 401 Unauthorized

After:

❯ ollama run deepseek-v3.1:671b-cloud
You need to be signed in to Ollama to run Cloud models.

To sign in, navigate to:
    https://ollama.com/connect?name=aaa&key=cbbb

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/ollama/ollama/pull/14057 **Author:** [@BruceMacD](https://github.com/BruceMacD) **Created:** 2/3/2026 **Status:** ✅ Merged **Merged:** 2/4/2026 **Merged by:** [@BruceMacD](https://github.com/BruceMacD) **Base:** `main` ← **Head:** `brucemacd/chat-cloud-signin` --- ### 📝 Commits (2) - [`f45f2fa`](https://github.com/ollama/ollama/commit/f45f2fa6692e5cb9c4d5f64224c985cf54f787a3) cmd: helpful error message for remote models - [`7b32333`](https://github.com/ollama/ollama/commit/7b323337c9800d82692148b518b078aac686d716) move cloud check before first log ### 📊 Changes **2 files changed** (+113 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `cmd/cmd.go` (+12 -1) 📝 `cmd/cmd_test.go` (+101 -0) </details> ### 📄 Description When trying to use cloud model with OLLAMA_HOST="ollama.com" while not signed in, a helpful error message is displayed. This should be the same experience for models which specify a remote instance. Before: ```bash ❯ OLLAMA_HOST=ollama.com ollama run deepseek-v3.1:671b You need to be signed in to Ollama to run Cloud models. ❯ ollama run deepseek-v3.1:671b-cloud Connecting to 'deepseek-v3.1:671b' on 'ollama.com' ⚡ >>> hi Error: 401 Unauthorized ``` After: ```bash ❯ ollama run deepseek-v3.1:671b-cloud You need to be signed in to Ollama to run Cloud models. To sign in, navigate to: https://ollama.com/connect?name=aaa&key=cbbb ``` --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-25 01:23:37 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#45737
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?