Copy an Answer, Read a Server's Manual, Keep Ten Threads Open
July 27, 2026 · InfraScout Team
A batch of smaller chat changes, each one a thing that had been quietly costing somebody a few seconds every day.
Copy a reply as markdown
An assessment finding usually has somewhere else to go — a ticket, an incident record, a report. Selecting an answer in the browser and copying it gave you rendered text with the structure stripped out: headings flattened, list markers gone, code blocks turned into runs of unindented lines.
Hovering an answer now reveals a copy button that puts the reply on your clipboard as raw markdown. Headings, lists, and fenced code arrive intact and render properly wherever markdown renders.
Where the answer cited sources, the copy carries them. Inline citation markers become plain numbered references, and a Sources footer lists the tools and web pages behind them, numbered to match. The numbering comes from the same source as the on-screen citations, so a copied answer's references cannot disagree with the ones you were looking at. An answer with no citations is copied byte for byte — which is the point of calling it raw.
The AI can read a server's own instructions
Many MCP servers publish usage instructions during their handshake: how their tools relate, which to reach for first, conventions their arguments follow. InfraScout was collecting that text and then never using it.
The AI can now read it on demand. Rather than injecting third-party text into the system prompt of every conversation — which would spend tokens on servers nobody is using and put outside text somewhere it carries more weight than it should — there is a tool the AI calls when it decides it needs a particular server's documentation. It can see which of your registered servers have published any, so it knows when reading is worth a turn.
You will see it happen as an ordinary step in the transcript: a read of the server's own documentation before the AI starts calling that server's tools. The text is treated as reference material from an outside source, not as instructions InfraScout follows.
This is chat only. Delegated runs, workflows, and raw MCP clients are not offered it.
Ten tabs, and titles that appear
The tab strip holds ten concurrent conversations, up from five. Behavior at the limit is unchanged: opening a conversation while full loads it into the active tab rather than pushing another one out.
Conversation titles now also appear without a reload. A title is derived server-side after the first turn, and it was being persisted correctly and never sent to the browser — so the tab and the panel header both sat on New conversation indefinitely while the title existed in the database the whole time. It arrives live now.
Fewer things flashing
Two interface annoyances, both from live updates being handled too bluntly.
Views that refresh on a live update used to collapse the entire page to loading skeletons and then repopulate — a full flash for a change that affected one row. A refresh now updates in place, so a busy view stops strobing.
And the MCP servers view gained entrance animation, which sounds cosmetic and matters slightly more than that: the server dropdown now shows each agent's platform icon and dims the agents that are offline, so picking a host that cannot currently do anything is visibly the wrong choice rather than a discovery you make afterward.
Nothing to enable
All of it is live. The copy button appears on hover over any AI answer.
See Chat for the full picture, and MCP Servers for the server-instructions side. Questions? info@infrascout.cloud.