Skip to content

LM Studio no longer ships a stale OpenAI model catalog - #2065

Open
tschuehly wants to merge 1 commit into
mainfrom
fix/lmstudio-stale-openai-catalog
Open

tschuehly wants to merge 1 commit into
mainfrom
fix/lmstudio-stale-openai-catalog

Conversation

@tschuehly

Copy link
Copy Markdown

Fixes #2064.

Why: embabel-agent-lmstudio-autoconfigure shipped its own models/openai-models.yml, a copy from #1092 that was never updated. When the LM Studio jar comes first on the classpath, that copy shadows the real OpenAI catalog, and newer OpenAI models (e.g. gpt-5.4, gpt-5.4-mini) are missing from the model list.

Change: delete the stale file. Nothing in the LM Studio module reads it.

Test: LmStudioCatalogTest asserts the LM Studio module ships no models/openai-models.yml. It failed before the deletion and passes after; the module's tests pass (14, 0 failures).

@igordayen

igordayen commented Sep 25, 2026 •

Copy link
Copy Markdown
Contributor

@tschuehly - could you please sign the commit? Which release would you like to target? thanks

Could you please also comment on:

special_handling:
      supports_temperature: false  #

Not required as well?

looping @azanux, @alexheifetz

@igordayen
igordayen self-requested a review September 25, 2026 18:41
The LM Studio autoconfigure jar carried its own models/openai-models.yml,
copied in #1092 and never updated. When it sorts first on the classpath it
shadows the OpenAI catalog, so newer OpenAI models such as gpt-5.4 are
missing from the model list. Nothing in the LM Studio module reads the file.

Fixes #2064

Signed-off-by: tschuehly <tschuehly@outlook.com>
@tschuehly
tschuehly force-pushed the fix/lmstudio-stale-openai-catalog branch from 267142c to 1d2e89e Compare September 26, 2026 07:05
@tschuehly

Copy link
Copy Markdown
Author

Thanks @igordayen!

  • Sign-off: done — rebased with --signoff and force-pushed; DCO is green.
  • Release: 1.5.3, please. The stale file shipped in 1.5.2.
  • supports_temperature: nothing is lost by dropping it. That block only ever affected OpenAI models, and only when this stale copy shadowed the real catalog. The real openai-models.yml in embabel-agent-openai-autoconfigure still sets supports_temperature: false (plus supports_top_p, uses_max_completion_tokens, …) for the GPT-5 family. LM Studio registers the local models it discovers itself and never reads this YAML. The new LmStudioCatalogTest guards against the copy coming back.

@sonarqubecloud

Copy link
Copy Markdown

@igordayen igordayen added this to the 1.5.3-Release🔵 milestone Sep 26, 2026
@igordayen

Copy link
Copy Markdown
Contributor

@tschuehly - assigned milestone 1.5.3 as requested, thanks

@igordayen igordayen left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tschuehly looks good, thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

LM Studio autoconfigure ships a stale openai-models.yml that shadows the OpenAI catalog

2 participants