GroundedCore / nexusdesk

# NexusDesk
**English** · 简体中文 · Website
> Chinese-speaking users: see the 简体中文 README.
**Self-hosted AI customer service that can retrieve, act, and hand off.**
NexusDesk is built for teams that need to keep customer service data on their own infrastructure. Agents retrieve knowledge, call business tools, and decide what to do next based on execution results. The Harness handles permissions, execution boundaries, memory, human handoff, and audit.
The Harness is not another agent; it is the engineering control layer around the agent execution loop.
**The default deployment requires only PostgreSQL.** PostgreSQL handles data storage, job queues, and cross-process messaging. Redis, dedicated message queues, Kubernetes, and other infrastructure can be added as throughput, latency, isolation, or availability requirements grow. The initial deployment still starts with one Compose file.
Quickstart · Production deployment · Core capabilities · Architecture
## Quickstart
Requires Docker and Docker Compose v2. On Docker Desktop, use Linux containers.
**Option 1: build locally.** The first run requires network access and compiles the frontend.
 [code] 
 [code] 
**Option 2: use the published image.**
 [code] 
Open **https://localhost:8080** and choose the `sample-support` conversation:
- Enter `发货需要多久？` to try knowledge Q&A.
- Enter `帮我创建工单` to try drafting, human confirmation, and ticket creation.
The quickstart uses a self-signed certificate, so the browser will warn on first access. See the deployment guide for certificate setup and LAN access.
Nine industry case sets are also included: 9 knowledge bases, 18 agent drafts, and 36 documents. Every resource name carries the `[案例]` prefix and can be filtered on the Agent page.
> **Security note:** the quickstart uses a mock model and does not represent real answer quality. The default credentials `admin / nexusdesk` are for local evaluation only and are not an authentication boundary. Keep the default `127.0.0.1` binding; if you expose the service, restrict access with a security group or firewall.
## Production deployment
Copy the configuration template, fill in role tokens and the external PostgreSQL connection, and enable Milvus / S3 as needed:
 [code] 
 [code] 
Open **http://localhost:8080** and enter the configured role token under Access and Policy. The platform can start without a default model; configure and publish a Chat profile, bind it to an agent, and then start a conversation.
The production topology includes six long-running services — API, Runtime Worker, Channel Worker, Knowledge Worker, Memory Worker, and Web — plus a one-shot migration task. See the deployment guide for HTTPS, backup, upgrade, and external access configuration.
## Core capabilities
| Capability | What it provides |
| --- | --- |
| Agent configuration and execution | Configure, publish, and roll back agents; run reasoning and tool calls through an asynchronous LangGraph ReAct loop |
| Knowledge and retrieval | Manage docume