Inferpal 1.7.9

Fifty-two fixes, and the first of them are about what you approve: permission rules now do what they say, an approval no longer writes over what you saved meanwhile or lands in another file, and an "Always" can no longer pass to a server you never approved.

What you approve

• Permission rules do what their comments say. The example rules in the documentation end with a comment (deny * \.env$ # never touch secrets), and copied as shown they matched nothing — .env could be written, rm -rf was not blocked. A # after a space now starts a comment.
• A command chained after an allowed one is no longer approved with it. A rule that auto-approves git also approved git status; Remove-Item -Recurse src, past the rule that denied Remove-Item. A command line is now approved only when every command on it is.
• What you save while an approval waits is no longer written over. If you saved the file — or VS Code's auto-save did — while the agent's change waited for your answer, approving wrote the older text back over your work. The change is now refused, your file is kept, and the agent reads it again.
• Text inserted by the agent goes to the file you approved, not to whichever file is active when you click.
• An "Always" given to one of your MCP tools can no longer pass to a repository's server whose name differs from yours only by punctuation (my.server next to your my-server). Such a server is not started, and the MCP status says which of yours it collides with.
• A file your permission rules protect no longer makes the agent give up the tool: it is told this path or command is refused, and carries on with its other edits.
• Visual Studio: a project's own build check is asked about again in another project — the command a repository declares in .inferpal/validators.json no longer runs unasked in the next solution you open.
• VS Code: Enter no longer approves a question you did not read. An approval asked outside an answer is now a dialog, as in Visual Studio, and Enter or Escape answers a card only when it is the only one waiting.
• VS Code: a link in an answer opens only if it is a web address — a vscode://… or ms-settings: link written by the model no longer launches a program.

Fixed, in every editor

• A settings file broken by a hand edit no longer costs you your settings. One comma too many in config.json, and the next setting you changed wrote the factory values back — model server, MCP servers and permission rules gone. Your settings are kept.
• Edit with AI, /fix, /refactor and /doc keep the nesting of files indented with two spaces or with tabs — a YAML key no longer moves out of its parent, a Python body no longer leaves its block.
• A failed build is no longer reported as a clean one, and a build that could not start (no project in the folder) is no longer counted as a compilation error.
• pytest and cargo runs that failed after their tests passed are red (pytest-cov's minimum coverage, a test binary that crashes later), and a pytest run longer than a minute no longer reads "nothing was proven".
• "Tests passed" only when tests ran, and a failing test run is no longer forgotten because a later check matched no test.
• /tdd runs the tests of a solution that is not at the root of your folder — with the solution in src/, every round used to say that no test ran.
• Windows: pytest's messages keep their accents, and a symbol outside the Windows code page no longer makes the run fail.
• A long file the agent writes no longer ends the run as raw text: a write cut at the answer's length limit is recognised, and the agent splits the work.
• A tool call with a parameter left unclosed is no longer run without its arguments — the whole test suite instead of the one test asked for.
• One broken tool call no longer takes the others down with it: the files the agent correctly asked to read are read.
• A reasoning model's summary or inline edit no longer vanishes because its reasoning mentioned a tool.
• The agent's closing answer fits a long conversation instead of overflowing the model and ending on a bare list of tools.
• A background task no longer mixes into the answer you are waiting for, and a failing command run in the background reports its failure instead of "exit code 0".
• Changing the embedding model no longer mixes two models in one index, which made semantic search return noise under a green status.
• The codebase search says what the index leaves out — files too large, a folder that could not be read — and a file busy during a rebuild (a build writing it) keeps its place in the index.
• Renaming and impact analysis follow edits to folders kept out of search (indexExclude), and the impact analysis no longer answers about another file of the same name.
• A language server that stops answering no longer slows the indexing down, ten seconds a file, in silence: it is set aside and the indexing goes on.
• @code and @tree no longer attach "nothing found": they say why nothing was attached.
• What you type after /explain, /review, /fix, /refactor, /doc and /test reaches the model — /fix the off-by-one in the loop fixes that.
• /debug stop the crash when the list is empty investigates — it no longer stops your debugging session. And /template name more words no longer clears the conversation.
• A conversation you clear is saved before it leaves — closing the editor right after /clear no longer loses it.
• /undo-run can be tried again when a file could not be given back (open in another program, say), and tries those files only.
• Signing in to an MCP server through Microsoft Entra, Keycloak, Okta and similar providers works, and asks only for the permissions the server needs.
• You can sign in to an MCP server your repository declares, or that Zed passes: it has its own card with a Sign in button.
• An MCP sign-in survives a provider that is briefly down, and with Visual Studio and VS Code both open, one no longer asks you to sign in again after the other renewed it.
• Signing in to one MCP server no longer signs you out of the others when the file holding your sign-ins could not be read at that moment.
• When an MCP tool fails, the agent is told what to do about it — no longer advice that contradicts the cause.

Fixed, in Visual Studio

• /fix-build builds the solution you have open — not the first one in the folder, which then reported the build as fixed.
• Opening another solution no longer overwrites that solution's last conversation, and /clear empties the right one.
• A background task runs in the solution you gave it, even when another solution is open by the time it starts.
• After you close the file you were working in, the agent no longer edits an old copy of another one.
• Tables in answers follow the theme — readable again after switching between dark and light.
• @file attaches the file as you see it, unsaved changes included.
• An accepted inline suggestion keeps your file's line endings.

Fixed, in VS Code

• Signing in to an MCP server works from a remote window (SSH, WSL, a container): the page opens in your browser, and wherever no browser can be opened, the sign-in says so at once instead of waiting five minutes.
• A question sent while settings are being applied is told so — and the approval questions waiting are no longer answered "no" for you.
• Inferpal stays in your editor's language, instead of switching to Windows' language when the MCP servers start.

Fixed, in Zed and the other agent-protocol editors

• A thread coming back after a pause takes every request sent meanwhile — no more "Unknown session", and a thread closed meanwhile stays closed.
• A /task report finishing right after an answer stays in the saved thread.
• Inferpal stays in your editor's language in every thread.
• The settings window's @docs page follows a reset of the window.