Clearer Chat Endings, and MCP Servers That Keep Your Credentials at Home
September 26, 2026 · InfraScout Team
Alongside interrupted responses that continue on their own, this release fixes several places where chat left you guessing, and tightens how InfraScout talks to the MCP servers you register. One of those changes can stop a misconfigured server from connecting, so if you administer MCP servers, read the last section.
An empty answer now says why it is empty
Two different events used to end the same way, with a blank reply.
When you press Stop while the AI is still thinking, the answer is now marked Stopped before the answer finished., both live and after a reload, and in the floating chat panel as well as the main view.
When a model spends its whole output allowance on reasoning and never gets to write the answer, the turn now ends in an error card that says so, with Retry beside it. It is not retried automatically, because the same request would most likely run out the same way. If a retry fails too, ask for a smaller step.
An attached playbook is the one to run
When you attach a playbook to a conversation and say "start the playbook", the AI now follows that playbook directly. Previously it often listed the available playbooks or asked which one you meant, even though you had just picked it.
The Context field is background, not a request
The Context field on the new-chat form is background for the AI, such as the scope or the environment. The AI deliberately does not act on instructions written there, so a request typed into it was silently ignored. The field's hint now says so: type what you want done in the message box once the conversation starts.
Conversations that were created but never received a message, usually because the first send failed or the tab closed in between, no longer pile up in your list as New conversation. They are cleared away automatically once they are more than a day old.
The tool catalog only offers servers that can answer
The chat tool catalog used to list an external MCP server's tool group even when the server was disabled, deleted, or used OAuth with no connected account. You could tick it, and the AI would then report that it had no access. Those groups are now left out.
The catalog also follows changes live. When an admin enables or disables a server, open chat panels pick up the change without a reload, and a selected group that disappears is removed from the selection.
MCP connections stay on the host you registered
Every connection to a registered MCP server is now pinned to the host in the URL you registered, and your credentials — static headers, the connected account's token, or a user's own token under per-user identity — are only ever sent there.
The change closes a gap in the older SSE (Legacy) transport, where the server tells the client which address to send its messages to. That address was followed even when it pointed at a different host, taking your credentials with it, so a misconfigured or compromised server could collect them. Agent-hosted servers that connect out to a remote URL get the same protection with agent version 0.33.1.
A server that splits its traffic across hosts no longer connects
If you have an SSE server whose message endpoint lives on a different host from its SSE URL, it now fails to connect, and the error names the refused host. Register the host that serves both, or switch the server to HTTP (Streamable) if it supports that transport.
Two smaller fixes apply to servers that use per-user identity. A user the server refuses — not assigned to its Entra application, or holding no role on the server — now sees that an administrator must grant them access, and the admin Test button reports Access denied and names which side refused. And a server form left open while another admin switched the server to per-user identity, or the enable toggle in the server list, can no longer quietly switch it back to the shared account.
More detail: Chat, MCP Servers and Per-User Identity for MCP Servers.
Questions or feedback? Reach us at info@infrascout.cloud.