Inferpal 1.8.0

With LM Studio, Qwen3.8 now spends its reasoning where you are waiting for it: a /check review comes back two to three and a half times sooner, and the small tasks Inferpal runs for you — titles, commit messages, summaries — no longer wait for it to think. /check reviews your whole change again, and a repository's MCP server is asked about again when the code it runs changes.

Reasoning models (LM Studio)

• A /check review on Qwen3.8 comes back two to three and a half times sooner. A question — /check included, with tools or without — now asks for a low reasoning effort: on Qwen3.8 27B, /check found the same issues in 38 seconds instead of 136 in English, and in 31 instead of 69 in French, and tool tasks pass as before. The level is sent only to a model LM Studio says takes it, so Gemma 4 and GLM 4.7 Flash are unchanged.
• gpt-oss is now always asked for low, the level LM Studio gives it by default: if you raised it in LM Studio, set it in Inferpal instead.
• Session titles, commit messages and summaries no longer wait for the model to think. They ask for no reasoning when LM Studio says the model can turn it off — Qwen3.8 27B then writes about 84 % fewer tokens for a summary.
• You choose the level. Settings → Server and models → Show advanced settings → Sampling and reasoning: one level for a question, one for an agent run (Server's, Low, Medium, High). Agent runs keep your server's setting by default: their time goes to the tools they run, not to reasoning.

/check

• /check reviews the whole change, with your checks on top. In a repository with checks, it reviewed the diff only against them and answered "all checks pass" on changes that broke something none of them named — the more checks you had written, the narrower the review. It now looks for any bug, regression or behaviour change, applies your checks as added criteria and says which of them pass. /check <name> still reviews against that one check only.

Security

• A repository's MCP server is asked about again when the code it runs changes, not only its definition. Your agreement to start a server your repository declares (.mcp.json, .vscode/mcp.json…) covered its command line: a script rewritten by a git pull — submodules included — was started without asking. The agreement now also covers the repository's files the server runs, checked again just before it starts and before it is restarted. In a git repository, what it writes beside itself is not part of it — but a file its definition names always is, even one git does not track, so a database named in its arguments asks again when it changes. A link that leads out of the repository is never followed. A server whose script you had agreed to is asked about once more after this update.
• MessagePack 2.5.303 in the VS Code host, for an advisory (GHSA-qhrr-8q5h-9q3h) on deserializing untrusted data into object. The host speaks JSON to VS Code and to ACP clients and never reads MessagePack from outside, so the affected path was not reachable. Visual Studio provides its own copy.