Theia API Documentation v1.75.0
    Preparing search index...

    Agent Plugins section of the Extensions view. A plugin is exactly one row: its skills and servers never appear as rows of their own, which would suggest they can be installed or removed alone.

    Implements

    Index

    Constructors

    Properties

    contextMenuRenderer: ContextMenuRenderer
    displayName: string = AGENT_PLUGINS_LABEL

    Human-readable label used as the group header in the view.

    fetchService: RegistryFetchService
    hoverService: HoverService
    installer: PluginInstaller
    installService: PluginInstallService
    logger: ILogger
    markdownRenderer: MarkdownRenderer
    mcpRegistrar: PluginMcpRegistrar
    messageService: MessageService
    onDidChange: Event<void> = ...

    Fired when the contribution's entries change (e.g. after install, refresh, or preference update).

    onDidChangeEmitter: Emitter<void> = ...
    priority: 300

    Agent Plugins sort below skills (200), which sort below MCP servers and extensions.

    searchFilter: RegistrySearchFilter
    searchToken: "@agent-plugins" = '@agent-plugins'

    @-prefixed token recognised in the search query to scope results to this contribution alone. Composable with the existing @installed / @builtin / @recommended mode tokens (e.g. @installed @mcp shows installed servers of type mcp-server only). When no type token appears in the query, all contributions are shown.

    Contributors are expected to start the token with @; without the prefix the search model may treat the token as a plain word in the free-text part of the query.

    toDispose: DisposableCollection = ...
    type: "agent-plugin" = 'agent-plugin'

    Stable, machine-readable identifier for the artifact type.

    windowService: WindowService

    Methods

    • Entries matching a user search. Each result carries its own searchableText so the view can rank hits from all contributions against a single query. Omit if this type does not participate in search.

      Contributions may ignore query when their internal state already reflects the current query (e.g. the VSX adapter, whose model is kept in sync with the search bar via the singleton VSXExtensionsSearchModel). In that case the contribution is expected to yield its current result set and let the view's cross-contribution fuzzy ranker handle the actual ordering.

      Parameters

      Returns Promise<Iterable<SearchResult, any, any>>