palyrad transport layer and uses specialized React hooks to manage domain-specific state.
Core Section Architecture
The console utilizes a centralized routing and content delivery mechanism. TheConsoleSectionContent component acts as a switch, rendering the appropriate domain view based on the current app.section state apps/web/src/console/ConsoleSectionContent.tsx#26-108.
Section-to-Code Mapping
| Section Name | React Component | Primary API Domain | Data Flow Source |
|---|---|---|---|
| Overview | OverviewSection | /console/v1/diagnostics | app.overviewDiagnostics |
| Sessions | SessionsSection | /console/v1/sessions | app.api.listSessions |
| Usage | UsageSection | /console/v1/usage | useUsageDomain |
| Memory | MemorySection | /console/v1/memory | app.memoryStatus |
| Skills | SkillsSection | /console/v1/skills | app.api.listSkills |
| Agents | AgentsSection | /console/v1/agents | app.api.listAgents |
| Channels | ChannelsSection | /console/v1/channels | app.channelsConnectors |
| Access | AccessSection | /console/v1/inventory | useInventoryDomain |
| Config | ConfigSection | /console/v1/config | useConfigDomain |
| Secrets | SecretsSection | /console/v1/secrets | app.api.listSecrets |
Technical Detail by Section
1. Overview & Operations
The Overview provides a high-level posture of the system, including attention items like pending approvals or degraded connectors apps/web/src/console/sections/OverviewSection.tsx#146-154. The Operations (Diagnostics) view provides lower-level runtime health, including model provider states, auth profile status, and self-healing incident logs apps/web/src/console/sections/OperationsSection.tsx#50-75.2. Usage & Cost Tracking
TheUsageSection visualizes token volume, run throughput, and estimated costs. It pushes time filters (24h, 7d, etc.) to the backend to ensure consistency between the UI and CLI exports apps/web/src/console/sections/UsageSection.tsx#145-147. It leverages useUsageDomain to fetch UsageTimelineBucket aggregates apps/web/src/console/sections/UsageSection.tsx#36-44.
3. Memory & Workspace
TheMemorySection manages the RAG (Retrieval-Augmented Generation) pipeline. It handles:
- Learning Queue: Reviewing “learning candidates” extracted from sessions apps/web/src/console/sections/MemorySection.tsx#158-163.
- Workspace Documents: Managing curated markdown files used as long-term context apps/web/src/console/sections/MemorySection.tsx#115-129.
- Recall Preview: Testing how specific queries retrieve data from session and workspace sources apps/web/src/console/sections/MemorySection.tsx#89-91.
4. Agents & Execution Backends
TheAgentsSection manages the agent registry. It includes a multi-step wizard for creating agents with specific workspace roots, tool allowlists, and execution backend preferences (e.g., Wasm vs. Native) apps/web/src/console/sections/AgentsSection.tsx#55-76.
5. Access & Inventory
This section bridges the gap between the web console and physical nodes. It manages:- Node Pairing: Minting codes and approving
NodePairingRequestViewobjects apps/web/src/console/sections/AccessSection.tsx#8-10. - Trust Review: Rotating or revoking certificates for devices in the
InventoryDeviceRecordapps/web/src/console/sections/AccessSection.tsx#129-135.
6. Config & Secrets
TheConfigSection provides a safe interface for mutating palyrad.toml. It supports redacted inspection, where sensitive values are masked unless explicitly revealed by the operator apps/web/src/App.config-access-support.test.tsx#37-40. The SecretsSection interacts with the palyra-vault via the /console/v1/secrets endpoint apps/web/src/App.config-access-support.test.tsx#70-88.
Sources: apps/web/src/console/sections/OverviewSection.tsx#100-155, apps/web/src/console/sections/UsageSection.tsx#56-93, apps/web/src/console/sections/MemorySection.tsx#104-180, apps/web/src/console/sections/AgentsSection.tsx#164-223, apps/web/src/console/sections/AccessSection.tsx#64-109
Data Flow Diagrams
Console Data Ingestion and Domain Routing
This diagram illustrates how theConsoleSectionContent acts as the dispatcher for domain-specific data fetched from the palyrad HTTP handlers.
Title: Console Domain Data Flow
Sources: apps/web/src/console/ConsoleSectionContent.tsx#26-108, crates/palyra-daemon/src/transport/http/handlers/console/mod.rs#1-30
Config and Secret Mutation Lifecycle
This diagram shows the transition from Natural Language Space (Operator Intent) to Code Entity Space (Vault and File System). Title: Config and Secret Mutation Flow Sources: apps/web/src/App.config-access-support.test.tsx#128-150, apps/web/src/console/sections/SecretsSection.tsx#1-10Section Capability Catalog
The console uses aCapabilityCatalog to determine which features are available based on the daemon’s deployment posture.
| Capability ID | Section | Dashboard Exposure | CLI Handoff Command |
|---|---|---|---|
config.mutate | Config | direct | N/A (Web Managed) |
gateway.access.verify_remote | Access | cli_handoff | palyra daemon dashboard-url --verify-remote |
support.bundle | Support | direct | N/A |
policy.explain | Operations | internal_only | N/A |