This directory is part of labsai/EDDI. It was the separate labsai/EDDI-Manager repository until 2026-09-15; its full history was imported here (git log -- ui/manager). Issues and pull requests go to labsai/EDDI. The UI is built into the EDDI jar by Maven from the repository root — see the root AGENTS.md (Build & Test Commands).

Admin dashboard for EDDI — the open-source multi-agent orchestration middleware for conversational AI.

EDDI Manager is a modern React SPA that ships inside the EDDI Docker image. It provides a visual workspace for building, testing, deploying, and monitoring AI agents — no code required.

🌐 Website: eddi.labs.ai · 📖 Docs: docs.labs.ai · 🐳 Docker: hub.docker.com/r/labsai/eddi

• Agent Builder — Create and configure agents with a drag-and-drop workflow pipeline
• Agent Studio — 3-panel workspace with live chat, debug drawer, and pipeline inspector
• Group Discussions — Orchestrate multi-agent conversations across 8 discussion styles
• LLM Configuration — Connect to 11 providers (OpenAI, Anthropic, Gemini, Ollama, etc.)
• Resource Editors — Form-based editors for rules, API calls, LLM configs, dictionaries, RAG, MCP, and more
• Secrets Vault — Manage encrypted API keys with vault references
• Global Variables — Deploy-wide configuration values for all agents (${vars:<key>} / {{vars.<key>}})
• Audit Trail — Timeline-based compliance and debugging viewer
• 11 Languages — English, German, French, Spanish, Portuguese, Chinese, Japanese, Korean, Arabic (RTL), Hindi, Thai

The easiest way to use EDDI Manager is via the main EDDI project:

# One-command installer (includes Manager)
curl -fsSL https://raw.githubusercontent.com/labsai/EDDI/main/install.sh | bash

Then open http://localhost:7070/manage.

See the EDDI README for full setup instructions.

If you want to develop the Manager UI itself:

# Prerequisites: Node.js ≥ 22.18 (Stryker 10's Babel 8 floor; the build pins 22.23.2), EDDI backend on localhost:7070
npm install
npm run dev          # Vite dev server on http://localhost:3000

The Vite dev proxy forwards API calls to the EDDI backend. If no backend is available, the Manager auto-starts in standalone mode with mock data (via MSW).

npm run test         # Vitest unit/component suite (run it for the current count)
npm run build        # Production build

• EDDI — Backend engine (Java 25, Quarkus)
• EDDI Chat UI — Embeddable chat widget, ui/chat of the same repository
• quarkus-eddi — Quarkus SDK

Apache 2.0