All Classes and Interfaces
Class
Description
Server-side registry of currently-live SSE streams.
One live SSE stream.
Builds the shared admin-ui chrome as a semantic-ui
UiAppShell:
a UiHeader (brand, burger, user widget) across the top, a
UiMenu side navigation with one entry per section, and the page
content filling the rest.Wraps every full
UiPage returned by an admin controller with the
shared layout (header: brand, nav, user widget, optional logout) — see
AdminLayout.Builds a per-request
AdminLayout from the current security context.Base class for full Admin-UI pages composed of
UiComponents.Tabbed detail view for a single agent: Details / Tools / Sessions.
Agent detail page with the Details / Tools / Sessions tabs.
Edit form for an agent definition.
Agent create/edit form.
Top-level list of agents: a search field, per-row Copy / Delete actions,
header "New Agent" action, and pagination that carries the search filter.
Top-level agent list — what the operator sees at
/admin/agents.The "API" section: the agent runtime's complete REST API, explorable via
the bundled springdoc Swagger UI (
/swagger-ui/index.html, fed by
/v3/api-docs).The chat page's attached-files panel: file name, chunk count and a Remove
action per attachment.
The chat UI's attach endpoint: same pipeline as the external
POST /api/sessions/{id}/files (via SessionFileService), but
the response is a UiPatch with a toast so the event bus can show
the outcome in place — the REST endpoint answers raw JSON instead.The chat-input form at the bottom of a
ChatPage — a single
textarea plus a context-sensitive Send / Stop button.The agent-session chat page.
Generates an example JSON payload from a JSON-Schema
Map (the shape
returned by Tool.parametersSchema()).Read-only detail view of a single LLM configuration with Edit and
Delete actions in the header.
Read-only detail page for one LLM configuration.
Edit form for an LLM configuration.
LLM configuration create/edit form.
Top-level list of all stored LLM configurations.
List of all LLM configurations at
/admin/llm-configs.Body of the "Test LLM config" modal dialog.
Detail pane of the working-memory inspector — two tabs:
Raw — the underlying record JSON via the json-viewer.
LLM View — what the model actually sees: compressed
stub if compression has run on the message, otherwise the
original content.
Master list of the working-memory inspector: every entry in the
upcoming LLM call window — the system prompt plus all windowed
messages — each as a clickable row that triggers a detail-pane
replace via a GET on the
?seq=… endpoint.Working-memory inspector page.
The main conversation list of a chat page.
The tool name and pretty-printed arguments out of a request's content JSON.
Supplies the pre-built sub-agent cards (with their nested child-task
trees) for a given parent
toolCallId.Lists pending migrations (bundled initial-data that is new or differs from
what is stored), grouped into one collapsible section per entity type — the
same layout the tool catalog uses.
Pending-migrations review page at
/admin/migrations.Computes and applies "migrations" — pending imports of bundled initial data
(classpath
initial-data/**) against what is currently stored.Supported entity types — also used as the id prefix and UI grouping label.
One top-level field that differs.
One reviewable change.
Whether a stored record is absent (NEW) or present-but-different (CHANGED).
Admin-UI endpoints for reviewing and applying migrations — pending imports of
bundled initial data (
classpath:initial-data/**) that is new or
differs from what is stored.One LLM-call roundtrip rendered as a three-tab card:
Response — prose first, then per-tool-call args
(json-viewer) followed by the matching persisted tool-result
block (collapsible).
The "Info" tab of a chat page — a read-only key/value list of
session metadata (id, agent, status, user, started-at, title) plus
a "Back to Agent" link.
Tabular view of an agent's chat sessions with Open / Delete row
actions and a header "New Session" action.
Shared static helpers used by every session-related UI assembler
(chat, working memory, traces) and by the cross-package
UI components in
ai.mindconnect.adminui.ui.component.Per-channel multiplexing fan-out used by
ActiveStreams.One past event held in the ring buffer.
Generic API over the
ActiveStreams registry.One tool-call or sub-agent-call card rendered as a collapsible
<details> list item.The agent's checklist for the current session — same items the LLM
sees in its prompt context via
{{ todo_list_md }}.Todo-list inspector page.
Read-only catalog of every tool the runtime's
ToolRegistry
knows about — the union of built-in ToolFactory tools and
MultiToolProvider-contributed tools.One catalog row: group (rubric), name, description, parameters schema and declared overrides schema.
Body of the "Test tool" modal for the top-level tool catalog — the same
shape as
ToolTestComponent, but identified by tool name
(no owning agent).Read-only catalog of all tools the runtime can provide.
Read-only detail view of one agent's tool.
Read-only tool detail page reached from the tool table's View
action.
Edit form for an agent's tool.
Tool create/edit form for an agent.
Read-only catalog of all available runtime tools at
/admin/tools.Tabular view of an agent's tools.
Body of the "Test tool" modal dialog.
One-shot execution of an
AgentTool with admin-supplied JSON
arguments.Detail-pane of the trace inspector — a stack of
RoundtripCardComponents for the selected turn, with consecutive
sub-agent roundtrips wrapped in a collapsible <details>
group so the parent stream stays readable.Master-list pane of the trace inspector — one row per top-level chat
turn.
LLM-call-trace inspector page.
A reusable UI building block that knows both its DOM id and how to
render itself as a
UiNode.Admin UI for vector stores: templates (the policies — backend, embedding
config, ingestion workflow) and the store instances created from them.
Workspace browser page — three scopes (SESSION / AGENT_USER / USER)
each rendered by a
WorkspaceScopeListComponent.One file listing for a single workspace scope (SESSION / AGENT_USER /
USER).