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

[PR #14383] doc: correct instructions for Goose CLI and Goose Desktop #25189

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

📋 Pull Request Information

Original PR: https://github.com/ollama/ollama/pull/14383
Author: @coolaj86
Created: 2/24/2026
Status: 🔄 Open

Base: main ← Head: patch-4

📝 Commits (1)

  • d7ed4ce doc: correct instructions for Goose CLI and Goose Desktop

📊 Changes

1 file changed (+6 additions, -5 deletions)

View changed files

📝 docs/integrations/goose.mdx (+6 -5)

📄 Description

Goose only works with Ollama Cloud by proxying it through local ollama serve.

Goose does NOT support OLLAMA_API_KEY.
It does NOT use any .env (config is at ~/.config/goose/config.yaml and keys are stored in the OS keychain). Ollama Cloud MUST be proxied through the local ollama instance via ollama serve.

None of the OpenAi, Ollama, nor Custom Provider options work with Ollama Cloud directly in any configuration that I was able to test.

Here are some of those flows for reference:

Screenshot 2026-02-23 at 8 33 11 PM image

Trying with any option other than Ollama and localhost lead to authentication errors.

In once case I did have a single working session using Custom Provider in the terminal, but when opening in Goose Desktop, or a second Goose CLI instance, it had the authentication errors.

🔄 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/14383 **Author:** [@coolaj86](https://github.com/coolaj86) **Created:** 2/24/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `patch-4` --- ### 📝 Commits (1) - [`d7ed4ce`](https://github.com/ollama/ollama/commit/d7ed4cef6729a586e188c2542f72abf803a85c16) doc: correct instructions for Goose CLI and Goose Desktop ### 📊 Changes **1 file changed** (+6 additions, -5 deletions) <details> <summary>View changed files</summary> 📝 `docs/integrations/goose.mdx` (+6 -5) </details> ### 📄 Description Goose only works with Ollama Cloud by proxying it through local `ollama serve`. Goose does NOT support `OLLAMA_API_KEY`. It does NOT use any `.env` (config is at `~/.config/goose/config.yaml` and keys are stored in the OS keychain). Ollama Cloud MUST be proxied through the local ollama instance via `ollama serve`. None of the _OpenAi_, _Ollama_, nor _Custom Provider_ options work with Ollama Cloud directly in any configuration that I was able to test. Here are some of those flows for reference: <img width="1052" height="912" alt="Screenshot 2026-02-23 at 8 33 11 PM" src="https://github.com/user-attachments/assets/4f586bea-b6a4-472a-a5eb-7b554132116f" /> <img width="1524" height="1444" alt="image" src="https://github.com/user-attachments/assets/a4c6e540-d853-4570-95ec-7612dafc98ee" /> Trying with any option other than Ollama and `localhost` lead to authentication errors. In once case I did have a single working session using Custom Provider in the terminal, but when opening in Goose Desktop, or a second Goose CLI instance, it had the authentication errors. --- <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-19 18:03:52 -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#25189
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?