dandri/simplex-chat
1
0
Fork 0
mirror of https://github.com/simplex-chat/simplex-chat.git synced 2026-03-31 01:05:55 +00:00
Code Issues Packages Projects Releases Wiki Activity

improve State Machine mermaid chart

Browse Source
This commit is contained in:
shum
2026-03-18 08:56:33 +00:00
parent 493cf569b1
commit d243fc89d4
1 changed files with 22 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

34
docs/plans/support-bot.md
View File

@@ -37,18 +37,28 @@ Two SimpleX Chat instances (separate databases) in one process:
### State Machine
```mermaid
stateDiagram-v2
Welcome --> TeamQueue: 1st customer text
Welcome --> GrokMode: /grok (first message)
Welcome --> TeamPending: /team (first message)
TeamQueue --> TeamQueue: customer text (forwarded to team)
TeamQueue --> GrokMode: /grok
TeamQueue --> TeamPending: /team
GrokMode --> TeamPending: /team (remove Grok)
GrokMode --> GrokMode: customer text (relay to API)
TeamPending --> TeamPending: customer text (forwarded to team)
TeamPending --> TeamLocked: team member sends message
TeamLocked --> TeamLocked: customer text (team sees directly)
flowchart TD
W([Welcome])
TQ([TeamQueue])
GM([GrokMode])
TP([TeamPending])
TL([TeamLocked])
W -->|1st text| TQ
W -->|/grok| GM
W -->|/team| TP
TQ -->|customer text| TQ
TQ -->|/grok| GM
TQ -->|/team| TP
GM -->|customer text| GM
GM -->|"/team (remove Grok)"| TP
TP -->|customer text| TP
TP -->|team member msg| TL
TL -->|customer text| TL
```
State is derived from group composition + chat history — not stored explicitly. The code uses 3 internal labels (`GROK`, `TEAM`, `QUEUE`) in prefixed headers on messages forwarded to the team group; Welcome/TeamPending/TeamLocked are implicit from message history. Note: there is no transition from GrokMode back to TeamQueue — the only commands are `/grok` and `/team`, so once Grok is active, the customer either continues with Grok or moves to team. TeamLocked is terminal (once a team member engages, the group stays locked).