Merged
Conversation
…rmated provider config found
DOsinga
approved these changes
Feb 24, 2026
u35tpus
pushed a commit
to u35tpus/goose
that referenced
this pull request
Feb 26, 2026
Signed-off-by: Oleg Levchenko <[email protected]>
10 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Added LM Studio as a declarative provider for Goose and fixed some issues.
While testing, I discovered that a recent PR (#7304) had added Kimi and Moonshot
provider configs with invalid JSON schema. This silently broke ALL declarative
provider loading — Groq, DeepSeek, Cerebras, Mistral, Inception, and OVHcloud were
all invisible in the UI because the loader aborted on the first malformed file. I
fixed the two broken JSON files and made the loader resilient so one bad file can't
take down the rest.
Also fixed a UX issue in the sidebar where clicking "Start New Chat" would get
stuck reusing a session that had failed to load. Sessions with errors and no messages
were being treated as empty/reusable. Now errored sessions are tracked and skipped
when looking for a session to reuse.