Conversation
Live backend, web and per-MCP-server tags with health, via CapabilityStatus, ActiveModelReportingBackend and the shared LlmBackendRegistration. Refs: ADFA-6279
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR introduces a live-updating row of capability tags under the chat input, replacing the static backend label. These tags provide users with immediate visibility into the agent's connected backend (including the active model name), web access status, and available tool sources (such as MCP servers and plugin tools). It also implements health probing across the MCP and OpenAI plugins, allowing the tags to reflect degraded states (e.g., unreachable servers or invalid API keys) in real-time, and resolves them automatically when the connection recovers.
Details
capability_tag_scrollandcapability_tag_grouptofragment_chat.xml. ImplementedCapabilityTagRowControllerto manage rendering, tapping (for details/settings), and long-pressing (for tooltips) of the tags.CapabilityMonitorandCapabilityReadersin AI-Core to manage the live state of backends and tool registries.ActiveModelReportingBackendand/orStatusReportingBackend. IntroducedServerHealthandMcpServerHealthto track and broadcast connectivity status.LlmBackendRegistrationrather than manually managing AI Core lifecycle listeners.plugin.min_ide_versionto26.41across all affected plugins to support the new capability tag contracts.Screen_Recording_20261002_172542_Code.on.the.Go.mp4
Screen_Recording_20261002_172715_Code.on.the.Go.mp4
Ticket
ADFA-6279
Observation
The tag row operates reactively using Flow collection, meaning it updates automatically when network connectivity changes, a server goes down, or a backend is switched. The individual plugins handle their own background polling (like the
PROBE_INTERVAL_MSfor MCP servers) to report degraded states without blocking the UI thread.