MChat

If Docker requires sudo on your machine, the script will use it automatically.

Docker (recommended)

```bash git clone https://github.com/windinwing/mchat.git cd mchat

make docker-up-lite

Path B — Docker full stack

git pull make docker-up-lite

**First clone**:

**Docker / MySQL commands**:

| Command | Description |
|---------|-------------|
| `make docker-up-lite` | Create `.env`, fix MySQL password, build & start |
| `make docker-down-lite` | Stop stack (keep volumes) |
| `make docker-logs-lite` | Tail logs |
| `make db-mysql-dev` | MySQL only (for `make dev`, default host port **3307**) |
| `make db-docker-reset-lite` | Wipe MySQL volume (password mismatch) |
| `MCHAT_RESET_FORCE=1 make reset-fresh` | Full wipe for clean re-test |

**MySQL (single lite config)**:

- Credentials: `mchat` / `mchat123`, database `mchat`, host port **3307** (see `ops/docker/.env`).
- `make setup` syncs `DATABASE_URL` in `src/backend/.env` automatically.
- Existing MySQL: `MCHAT_SETUP_MYSQL=0 make setup` and set `DATABASE_URL` yourself.
- `Access denied for user 'mchat'`: `make db-docker-reset-lite && make setup`.
- `make dev` stops Docker frontend/backend if they occupy port 5173 (MySQL is kept).

**Step by step** (without full `make setup`):

Docker variants

Quick start

Widget demo

Vertical channel configuration (Agent)

API docs: http://localhost:3001/docs

API overview

See docs/api.md or /docs (Swagger) after startup.

Workflow orchestration (Beta)

Workflow orchestration

MChat Workflow chains multiple Skills into reusable pipelines — not just one-shot chat, but multi-step automation with parallel branches, conditional routing, human approval, loop iteration, node groups, and structured outputs (reports, exports, alerts).

ComfyUI-style visual graph editor (Admin → Workflows → Edit Graph):

• Full-screen canvas with node tree sidebar, template gallery, run history, and results overlay
• Double-click to search — ComfyUI-style command palette for instant node insertion
• Node types: start · skill · condition (10 operators) · approval · merge · batch (loop) · group (visual) · end
• Node groups — select nodes → Cmd/G to create a colored, collapsible, resizable group frame
• Payload mapper — ${input.keyword}, ${nodes.<id>.result.xxx}, ${item} templates per node; type-preserving variable linking
• Batch / Loop — iterate a list, run sub-workflow per item with ${item} context, concurrent execution
• Condition — 10 operators (==, !=, >, <, >=, <=, contains, not_contains, startswith, endswith); both left and right support template variables
• Approval — pause a run until an operator approves or rejects in the admin UI
• Merge — wait for parallel branches, then feed downstream chart/export steps

Templates: built-in flows such as Patent Multi-Dimension Report (search → parallel analysis → merge → chart/Excel/Word/PPT). Browse templates in the gallery with mini graph preview, filter by category, and apply with one click. Save any workflow as a reusable template.

Example: one patent-search skill can appear in many nodes with different payloads — command: search for retrieval, command: analysis + dimension: applicant|ipc|… for parallel analytics, then patent-report for export.

Getting started

1. make setup && make dev (or make docker-up-lite)
2. Install skills (e.g. patent-search, patent-report) under Admin → Skills
3. Open Admin → Workflows — use a template or build a graph, then Run once
4. For scheduled runs: start the worker — make dev-worker or set WORKER_ENABLED=true in .env

Complete guide: Workflow Orchestrator · 中文版 · Product tour · API: docs/api.en.md#workflows-beta