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

[GH-ISSUE #11604] New UI Opens no matter what on app open #69721

New Issue
Open
opened 2026-05-04 18:57:03 -05:00 by GiteaMirror · 17 comments
GiteaMirror commented 2026-05-04 18:57:03 -05:00
Owner
Copy Link

Originally created by @JayTheXXVII on GitHub (Jul 31, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/11604

Originally assigned to: @BruceMacD on GitHub.

What is the issue?

New UI opens automatically on app launch instead of opening just a background task for Ollama.
Current fix = downgrade to v0.9.6

Relevant log output

OS

Windows

GPU

No response

CPU

No response

Ollama version

ollama v0.10+

Originally created by @JayTheXXVII on GitHub (Jul 31, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/11604 Originally assigned to: @BruceMacD on GitHub. ### What is the issue? New UI opens automatically on app launch instead of opening just a background task for Ollama. Current fix = downgrade to v0.9.6 ### Relevant log output ```shell ``` ### OS Windows ### GPU _No response_ ### CPU _No response_ ### Ollama version ollama v0.10+
GiteaMirror added the appfeature request labels 2026-05-04 18:57:04 -05:00
GiteaMirror commented 2026-05-04 18:57:08 -05:00
Author
Owner
Copy Link

@FringeNet commented on GitHub (Jul 31, 2025):

Do you have it enabled as a startup app in task manager? It shouldn't open if it's enabled, it should just start the background task

<!-- gh-comment-id:3141008353 --> @FringeNet commented on GitHub (Jul 31, 2025): Do you have it enabled as a startup app in task manager? It shouldn't open if it's enabled, it should just start the background task
GiteaMirror commented 2026-05-04 18:57:10 -05:00
Author
Owner
Copy Link

@JayTheXXVII commented on GitHub (Jul 31, 2025):

I may have misrepresented my issue.

When I click on Ollama.app.exe in v0.9.6 and prior it opens silently in the background without the newly added UI,
When I click on Ollama.app.exe in v0.10+ it opens silently alongside the new UI, which is fantastic, but doesn't have any means of launching without the new UI (To my knowledge)

<!-- gh-comment-id:3141081600 --> @JayTheXXVII commented on GitHub (Jul 31, 2025): I may have misrepresented my issue. When I click on Ollama.app.exe in v0.9.6 and prior it opens silently in the background without the newly added UI, When I click on Ollama.app.exe in v0.10+ it opens silently alongside the new UI, which is fantastic, but doesn't have any means of launching without the new UI (To my knowledge)
GiteaMirror commented 2026-05-04 18:57:12 -05:00
Author
Owner
Copy Link

@FringeNet commented on GitHub (Jul 31, 2025):

I think that should be expected on a manual launch.
I tested this situation in a VM using latest release.
When I have it enabled as a startup app, it launches silently.

Is there a reason you would rather launch it manually just to use it in the background?

<!-- gh-comment-id:3141087949 --> @FringeNet commented on GitHub (Jul 31, 2025): I think that should be expected on a manual launch. I tested this situation in a VM using latest release. When I have it enabled as a startup app, it launches silently. Is there a reason you would rather launch it manually just to use it in the background?
GiteaMirror commented 2026-05-04 18:57:15 -05:00
Author
Owner
Copy Link

@atorosto commented on GitHub (Jul 31, 2025):

enabled as a startup app

Why would we want it running in the background all the time? Seems redundant and unnecessary. There should be an option to start and stop it without launching the UI.

<!-- gh-comment-id:3141127784 --> @atorosto commented on GitHub (Jul 31, 2025): > enabled as a startup app Why would we want it running in the background all the time? Seems redundant and unnecessary. There should be an option to start and stop it without launching the UI.
GiteaMirror commented 2026-05-04 18:57:17 -05:00
Author
Owner
Copy Link

@FringeNet commented on GitHub (Jul 31, 2025):

PS C:\Users\FringeNet> ollama serve

Then Ctrl + C to stop it.

I have mine running in the background all the time, beats stopping and starting unnecessarily.

<!-- gh-comment-id:3141151271 --> @FringeNet commented on GitHub (Jul 31, 2025): ```PS C:\Users\FringeNet> ollama serve``` Then ```Ctrl + C``` to stop it. I have mine running in the background all the time, beats stopping and starting unnecessarily.
GiteaMirror commented 2026-05-04 18:57:19 -05:00
Author
Owner
Copy Link

@atorosto commented on GitHub (Jul 31, 2025):

This is not what it was before. It needs a checkbox "Start minimized" in the settings.

<!-- gh-comment-id:3141160501 --> @atorosto commented on GitHub (Jul 31, 2025): This is not what it was before. It needs a checkbox "Start minimized" in the settings.
GiteaMirror commented 2026-05-04 18:57:22 -05:00
Author
Owner
Copy Link

@FringeNet commented on GitHub (Jul 31, 2025):

Image
<!-- gh-comment-id:3141179770 --> @FringeNet commented on GitHub (Jul 31, 2025): <img width="200" height="150" alt="Image" src="https://github.com/user-attachments/assets/1d9df13c-7153-4f62-9ecc-4456ca526d44" />
GiteaMirror commented 2026-05-04 18:57:23 -05:00
Author
Owner
Copy Link

@dhiltgen commented on GitHub (Jul 31, 2025):

@JayTheXXVII any CLI commands that interact with the server will automatically launch the desktop app in background mode if the server isn't already running. (e.g., ollama ps or ollama run ...) Also, when launched at login time, the app will start in the background as well.

<!-- gh-comment-id:3141358265 --> @dhiltgen commented on GitHub (Jul 31, 2025): @JayTheXXVII any CLI commands that interact with the server will automatically launch the desktop app in background mode if the server isn't already running. (e.g., `ollama ps` or `ollama run ...`) Also, when launched at login time, the app will start in the background as well.
GiteaMirror commented 2026-05-04 18:57:26 -05:00
Author
Owner
Copy Link

@moogman commented on GitHub (Aug 1, 2025):

Even in the case where you run the desktop app in background mode.. when you click Open Ollama in the taskbar, there is then no way to close it. Clicking X on the open ollama window should intuitively just close the window, not "keep it open but move it to behind other windows".

<!-- gh-comment-id:3144192301 --> @moogman commented on GitHub (Aug 1, 2025): Even in the case where you run the desktop app in background mode.. when you click Open Ollama in the taskbar, there is then no way to close it. Clicking X on the open ollama window should intuitively just close the window, not "keep it open but move it to behind other windows".
GiteaMirror commented 2026-05-04 18:57:28 -05:00
Author
Owner
Copy Link

@dhiltgen commented on GitHub (Aug 1, 2025):

@moogman I haven't been able to reproduce what you describe. When I close the chat or settings window on mac or windows, the window disappears. Are you running the latest version of Ollama (currently 0.10.1)? What OS are you on?

<!-- gh-comment-id:3145169428 --> @dhiltgen commented on GitHub (Aug 1, 2025): @moogman I haven't been able to reproduce what you describe. When I close the chat or settings window on mac or windows, the window disappears. Are you running the latest version of Ollama (currently 0.10.1)? What OS are you on?
GiteaMirror commented 2026-05-04 18:57:29 -05:00
Author
Owner
Copy Link

@moogman commented on GitHub (Aug 4, 2025):

Yep, Ollama 0.10.1, on Mac OS.

Steps to reproduce:

  1. Load ollama in headless mode (e.g. ollama ls).
  2. Tab switch with Cmd-Tab. Notice that ollama doesn't appear in the list - Good.
  3. Click ollama in taskbar and Open Ollama. Notice that the ollama chat window shows up.
  4. Close that chat window.
  5. Tab switch with Cmd-Tab. Notice that ollama is in the list - Bad. You can't completely remove/close the chat window, you can only effectively move it to the background / tab-switch away.

This is slightly different to the original issue but I think it has the same root cause and it will have the same fix. Thanks!

<!-- gh-comment-id:3149998630 --> @moogman commented on GitHub (Aug 4, 2025): Yep, Ollama 0.10.1, on Mac OS. Steps to reproduce: 1. Load ollama in headless mode (e.g. ollama ls). 2. Tab switch with Cmd-Tab. Notice that ollama doesn't appear in the list - Good. 3. Click ollama in taskbar and Open Ollama. Notice that the ollama chat window shows up. 4. Close that chat window. 5. Tab switch with Cmd-Tab. Notice that ollama *is* in the list - Bad. You can't completely remove/close the chat window, you can only effectively move it to the background / tab-switch away. This is slightly different to the original issue but I think it has the same root cause and it will have the same fix. Thanks!
GiteaMirror commented 2026-05-04 18:57:31 -05:00
Author
Owner
Copy Link

@kullervo-wanona commented on GitHub (Aug 6, 2025):

There are cases where the Ollama server needs to be restarted multiple times in my application (I have to interrupt the server sometimes manually, this is a requirement in my application). Having a simple option available in the settings where it basically disables the chat UI launching automatically would be immensely helpful for this reason. This option can be disabled by default.

This would not change the default behavior. People may have reasons to relaunch the server outside of a startup (my setup launches the chat UI during startup as well for some reason, not sure if this is intended or not). Please consider adding this as a feature. Feel free to close #11690 if you consider it a replicate request.

Thank you.

<!-- gh-comment-id:3158965561 --> @kullervo-wanona commented on GitHub (Aug 6, 2025): There are cases where the Ollama server needs to be restarted multiple times in my application (I have to interrupt the server sometimes manually, this is a requirement in my application). Having a simple option available in the settings where it basically disables the chat UI launching automatically would be immensely helpful for this reason. This option can be disabled by default. This would not change the default behavior. People may have reasons to relaunch the server outside of a startup (my setup launches the chat UI during startup as well for some reason, not sure if this is intended or not). Please consider adding this as a feature. Feel free to close [#11690](https://github.com/ollama/ollama/issues/11690) if you consider it a replicate request. Thank you.
GiteaMirror commented 2026-05-04 18:57:35 -05:00
Author
Owner
Copy Link

@jsmith173 commented on GitHub (Oct 18, 2025):

I am experiencing the same issue on Windows 11 with a recent version of Ollama, where the UI window pops up every time an API request is triggered. This behavior is very disruptive, especially for end-user applications that rely on the background API service.
Is there any progress or an update on implementing an option to disable this pop-up functionality? A solution is needed to restore the previous silent, background-only behavior for API usage. Thank you for your work!

<!-- gh-comment-id:3417850740 --> @jsmith173 commented on GitHub (Oct 18, 2025): I am experiencing the same issue on Windows 11 with a recent version of Ollama, where the UI window pops up every time an API request is triggered. This behavior is very disruptive, especially for end-user applications that rely on the background API service. Is there any progress or an update on implementing an option to disable this pop-up functionality? A solution is needed to restore the previous silent, background-only behavior for API usage. Thank you for your work!
GiteaMirror commented 2026-05-04 18:57:39 -05:00
Author
Owner
Copy Link

@dhiltgen commented on GitHub (Oct 18, 2025):

every time an API request is triggered

@jsmith173 can you clarify? Are you using the CLI, invoke-webrequest, the Python SDK, the JS SDK, or some other mechanism to call the API at http://localhost:11434? (and are you using an alternate port, or bind address?)

<!-- gh-comment-id:3418736551 --> @dhiltgen commented on GitHub (Oct 18, 2025): > every time an API request is triggered @jsmith173 can you clarify? Are you using the CLI, `invoke-webrequest`, the [Python SDK](https://github.com/ollama/ollama-python), the [JS SDK](https://github.com/ollama/ollama-js), or some other mechanism to call the API at `http://localhost:11434`? (and are you using an alternate port, or bind address?)
GiteaMirror commented 2026-05-04 18:57:42 -05:00
Author
Owner
Copy Link

@jsmith173 commented on GitHub (Oct 19, 2025):

It's true that the Ollama UI window doesn't appear for every request, but it does pop up when our program starts. At startup, our program runs the Ollama model lister. For other requests we're using the LangChain OpenAI Python interface. For the end user, it's inconvenient because the Ollama UI window covers our app. This issue didn't occur previously. Previously, only the Ollama tooltip in the system tray became visible.

<!-- gh-comment-id:3419259821 --> @jsmith173 commented on GitHub (Oct 19, 2025): It's true that the Ollama UI window doesn't appear for every request, but it does pop up when our program starts. At startup, our program runs the Ollama model lister. For other requests we're using the LangChain OpenAI Python interface. For the end user, it's inconvenient because the Ollama UI window covers our app. This issue didn't occur previously. Previously, only the Ollama tooltip in the system tray became visible.
GiteaMirror commented 2026-05-04 18:57:45 -05:00
Author
Owner
Copy Link

@BruceMacD commented on GitHub (Oct 22, 2025):

Thanks for the reports on this. Seems like this was caused by some window focus behavior on Windows that prevented multiple apps from running, but didn't respect the --hide flag.

This should be resolved in the next release but if that's not the case I'm happy to re-open and keep investigating.

<!-- gh-comment-id:3430066680 --> @BruceMacD commented on GitHub (Oct 22, 2025): Thanks for the reports on this. Seems like this was caused by some window focus behavior on Windows that prevented multiple apps from running, but didn't respect the `--hide` flag. This should be resolved in the next release but if that's not the case I'm happy to re-open and keep investigating.
GiteaMirror commented 2026-05-04 18:57:45 -05:00
Author
Owner
Copy Link

@moogman commented on GitHub (Oct 22, 2025):

This isn't just with Windows - see https://github.com/ollama/ollama/issues/11604#issuecomment-3144192301

Ideally this wouldn't have been closed until it was actually fixed/released. Or at least tagged with the release - is there an indication on what release id/version this will be in so we can verify?

<!-- gh-comment-id:3430670448 --> @moogman commented on GitHub (Oct 22, 2025): This isn't just with Windows - see https://github.com/ollama/ollama/issues/11604#issuecomment-3144192301 Ideally this wouldn't have been closed until it was actually fixed/released. Or at least tagged with the release - is there an indication on what release id/version this will be in so we can verify?
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 app 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#69721
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?