Inferpal 1.7.7

Visual Studio 2022 joins Visual Studio 2026, moving from Continue or Roo Code takes one command, and Zed, the JetBrains IDEs, Neovim and Emacs get Inferpal's settings window — in your browser. Plus sixteen fixes.

Visual Studio 2022

• The same extension now installs and runs in Visual Studio 2022 (17.14 and later), not only in Visual Studio 2026: the chat and the agent with its approvals, inline suggestions, the change preview, /debug and the build banner.

Coming from Continue or Roo Code: /import

• /import continue reads your Continue configuration, /import roo the file Roo Code's settings export. A card lists, item by item, what Inferpal can take — the model server and the models by role, the context window, rules and system messages, prompts and custom modes as commands, MCP servers, documentation sites, allowed and denied commands as approval rules — and, folded underneath, everything else in the file with the reason it stays. A hosted provider is never imported, the commands Roo let run without asking are offered unticked, and nothing is written until you apply; your settings file is copied aside first. In Visual Studio, in VS Code, and in the agent-protocol editors.
• Commands for every workspace. A prompts folder beside Inferpal's settings holds commands available in every workspace — it is where /import puts them. A project's own command of the same name still wins.

Settings in Zed, the JetBrains IDEs, Neovim and Emacs

• The settings window, in your browser. The same seven pages as in Visual Studio and VS Code, with the Test button, the models loaded right now and the model suggestions. Your editor offers Open Inferpal's settings the first time; after that, type /settings in any thread. What you save applies from your next question, in the threads already open too; a model you picked in a thread stays that thread's. The page is served on your machine only, under an address nobody else can guess, and reaches the settings and nothing else.
• /settings also opens the settings from the chat in Visual Studio and VS Code.
• The sound at the end of a long run can be turned off in Visual Studio: Settings › Language and appearance. It stays on by default.

Fixed, in every editor

• Approving a change to several files names every file. The card said "Change a file" and named only the first one; it now counts them and names each. A rename is asked in your language, and says when some files could not be scanned.
• The approval card colours the change again when the agent edits several places at once, renames a symbol, deletes or restores a file — removed lines in red, added lines in green.
• /undo-run can still undo an agent's edit after many more questions. Fifteen questions after an edit, it said there was nothing to undo. And with Visual Studio and VS Code open on the same folder, one editor no longer deletes the backup the other needs.
• Visual Studio and VS Code on the same folder each get their own last conversation back. Closing Visual Studio and asking one question in VS Code lost Visual Studio's conversation; starting a new one in VS Code emptied Visual Studio's.
• A documentation source added in one window no longer replaces one added in another — it used to vanish from the settings, its pages from the search, without a word.
• Background tasks no longer load a second model. Naming a session or summarizing older turns used the chat model even in Agent mode — loading it next to the agent's model, often too slowly to finish. They now use the model already loaded.
• A context window left at 0 is no longer reported as "0". /hardware and the support bundle now say the server chooses, and name the window it loaded.
• Continue's MCP server files with multi-line values or YAML anchors are read, instead of being refused as unreadable.

Fixed, in Visual Studio

• The "last build failed" banner comes up again, with its button to fix the errors.
• A window no longer brings back another window's conversation — a solution opened for the first time could restore the conversation of a window that had no solution open, and the other way round.

Fixed, in VS Code

• A long Visual Studio conversation is no longer cut when VS Code saves it. VS Code saved only the last 2,000 entries it shows, and the oldest messages were lost — in the file Visual Studio had kept whole.
• A command's reply no longer looks like the model's answer: it shows as a notice at once, not only after a reload.
• The send button is no longer cut off in a narrow side bar.

Fixed, in Zed and the other agent-protocol editors

• Two threads no longer share their model. A model picked in one thread was the one the other threads asked, while their model selector still showed their own.
• Stop works from the first instant. A Stop pressed while Inferpal was still reading attached files was lost: the whole turn ran afterwards, file changes included, under a reply that said it was cancelled.
• An older thread no longer answers "Unknown session". With more than four threads open, the oldest idle one was closed and the next message in it failed; it now reopens with its conversation.