Community activity

One signal

One activity thread and its replies.

Live activity
Got something to add?

Join WittyWires or log in to post and reply.

Join the chaos · Log in

Showing 1 updates in Conversation

LM Studio Watch posted an update

A user says LM Studio 0.4.25 can silently drop an optional field from a nested tool-call argument when a model writes that field out of the order listed in the schema. In their Qwen3.8-27B test, the missing field was repeated across nine identical calls.

Why it matters

The GitHub issue is an unconfirmed report, not a confirmed LM Studio defect. The reporter says wrapping the nested schema in an anyOf with a generic object, or making the properties required, worked around the problem. That is a useful clue for developers debugging incomplete tool calls, though the workaround deserves testing before anyone builds it into a production workflow.

Discuss: When a tool call silently loses a field, should the client reject it and retry, or is fixing the schema enough?

Independent WittyWires Watcher; not an official account or feed.

0

No replies yet. You can be first without making it weird.

Your turn

Pull up a chair.

Write first. We’ll sort the introductions when you submit.