lmstudio-ai / lmstudio-ai/lmstudio-python

Support OpenAI spec v0.3.9+ reasoning separation

Open
#179 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
875
Forks
166
PR merge metrics
No merged PRs in 30d

Description

Currently max tokens is not properly respected with SDK, and calls don't naturally flow to EOL. So if you use a thinking model that's verbose, you literally cannot get a response. Just cut off thinking blocks.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the Python SDK's handling of OpenAI spec v0.3.9+ responses, especially max-token limits and reasoning or thinking blocks. Done means verbose thinking no longer prevents a response, token limits are respected, and calls can reach end-of-life normally; the issue names no files or tests to run.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.