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

[PR #15072] launch: set default model as active selection in vscode copilot chat #40876

New Issue
Open
opened 2026-04-23 01:40:06 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-23 01:40:06 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/ollama/ollama/pull/15072
Author: @hoyyeva
Created: 3/26/2026
Status: 🔄 Open

Base: main ← Head: hoyyeva/vscode-improve

📝 Commits (2)

  • 8b8bcf0 launch: set default model as active selection in vscode copilot chat
  • 7a23060 wip

📊 Changes

2 files changed (+254 additions, -18 deletions)

View changed files

📝 cmd/launch/vscode.go (+84 -18)
📝 cmd/launch/vscode_test.go (+170 -0)

📄 Description

  • When launching vscode via ollama launch vscode, the configured model is now set as the active selection in copilot chat's model picker
  • Previously, ShowInModelPicker only controlled model visibility — users would still see auto or their last manually selected model after launch
  • Writes the primary model to chat.currentLanguageModel.panel and chat.currentLanguageModel.editor in vscode's state database, using cached numeric IDs when available

Known limitation
After vscode restarts, users may still see a brief cycle: the previous model → "auto" → the configured model. This delay is caused by Copilot Chat's extension initialization — it resets the selection to "auto" while it re-discovers models from the ollama api, and only applies the state DB selection after discovery completes. This is controlled by the copilot chat extension.

🔄 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/15072 **Author:** [@hoyyeva](https://github.com/hoyyeva) **Created:** 3/26/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `hoyyeva/vscode-improve` --- ### 📝 Commits (2) - [`8b8bcf0`](https://github.com/ollama/ollama/commit/8b8bcf0952b04aa0dcf17954574628237c0c2f16) launch: set default model as active selection in vscode copilot chat - [`7a23060`](https://github.com/ollama/ollama/commit/7a2306087bcbea05b498370fc58f335ea15bc103) wip ### 📊 Changes **2 files changed** (+254 additions, -18 deletions) <details> <summary>View changed files</summary> 📝 `cmd/launch/vscode.go` (+84 -18) 📝 `cmd/launch/vscode_test.go` (+170 -0) </details> ### 📄 Description - When launching vscode via `ollama launch vscode`, the configured model is now set as the active selection in copilot chat's model picker - Previously, `ShowInModelPicker` only controlled model visibility — users would still see `auto` or their last manually selected model after launch - Writes the primary model to `chat.currentLanguageModel.panel` and `chat.currentLanguageModel.editor` in vscode's state database, using cached numeric IDs when available **Known limitation** After vscode restarts, users may still see a brief cycle: `the previous model → "auto" → the configured model`. This delay is caused by Copilot Chat's extension initialization — it resets the selection to "auto" while it re-discovers models from the ollama api, and only applies the state DB selection after discovery completes. This is controlled by the copilot chat extension. --- <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-23 01:40:06 -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#40876
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?