github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-07 16:40:08 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #13200] Feature Proposal: GUI Support for Remote Ollama Instances #70785

New Issue
Closed
opened 2026-05-04 22:58:22 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-05-04 22:58:22 -05:00
Owner
Copy Link

Originally created by @jonameijers on GitHub (Nov 21, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/13200

Note: I have a working implementation of this feature that is nearly complete. Before submitting a pull request, I wanted to open this issue to ensure the change aligns with Ollama's roadmap and to gather feedback from the maintainers, as this is a non-trivial change per the contribution guidelines.

Problem Statement
Users who run Ollama on a remote server cannot currently use the Ollama GUI application to connect to their remote instance. While the CLI supports connecting to remote hosts via the OLLAMA_HOST environment variable, the GUI application is hardcoded to connect only to localhost:11434. This creates a fragmented user experience.

Why the change is important

  • Feature Parity: The CLI already supports remote connections. The GUI should offer equivalent functionality.
  • Incomplete Implementation: The GUI currently offers a switch for "Expose Ollama to the network" but lacks the complementary ability to connect to a remote instance. This creates an asymmetric experience where users can host but cannot join.
Originally created by @jonameijers on GitHub (Nov 21, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/13200 Note: I have a working implementation of this feature that is nearly complete. Before submitting a pull request, I wanted to open this issue to ensure the change aligns with Ollama's roadmap and to gather feedback from the maintainers, as this is a non-trivial change per the contribution guidelines. **Problem Statement** Users who run Ollama on a remote server cannot currently use the Ollama GUI application to connect to their remote instance. While the CLI supports connecting to remote hosts via the OLLAMA_HOST environment variable, the GUI application is hardcoded to connect only to localhost:11434. This creates a fragmented user experience. **Why the change is important** - Feature Parity: The CLI already supports remote connections. The GUI should offer equivalent functionality. - Incomplete Implementation: The GUI currently offers a switch for "Expose Ollama to the network" but lacks the complementary ability to connect to a remote instance. This creates an asymmetric experience where users can host but cannot join.
GiteaMirror added the feature request label 2026-05-04 22:58:22 -05:00
GiteaMirror commented 2026-05-04 22:58:29 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Nov 21, 2025):

The ollama app supports the same way of connecting to a remote host as the CLI. Set OLLAMA_HOST before starting the app and it will connect to the remote host.

0.13.0, OLLAMA_HOST not set (or rather masked by putting an x at the start of the variable name):

Image

Only two local models listed

Image

0.13.0, OLLAMA_HOST set:

Image

Many models only found on the remote server listed:

Image
<!-- gh-comment-id:3565016682 --> @rick-github commented on GitHub (Nov 21, 2025): The ollama app supports the same way of connecting to a remote host as the CLI. Set `OLLAMA_HOST` before starting the app and it will connect to the remote host. 0.13.0, `OLLAMA_HOST` not set (or rather masked by putting an `x` at the start of the variable name): <img width="616" height="239" alt="Image" src="https://github.com/user-attachments/assets/fe3885dd-046d-4e79-8c19-e7e10ddae4bf" /> Only two local models listed <img width="802" height="509" alt="Image" src="https://github.com/user-attachments/assets/68c14898-8cbc-44db-957f-4cabf50703f6" /> 0.13.0, `OLLAMA_HOST` set: <img width="613" height="238" alt="Image" src="https://github.com/user-attachments/assets/5525822a-4f29-4751-8775-edc4233422e8" /> Many models only found on the remote server listed: <img width="800" height="514" alt="Image" src="https://github.com/user-attachments/assets/73f9a5b5-1c03-42cf-b55b-85e5a1a733bb" />
GiteaMirror commented 2026-05-04 22:58:34 -05:00
Author
Owner
Copy Link

@FHaggs commented on GitHub (Feb 19, 2026):

Can we have this at the settings?

<!-- gh-comment-id:3928881891 --> @FHaggs commented on GitHub (Feb 19, 2026): Can we have this at the settings?
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 feature 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#70785
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?