opensource/mateclaw
2
0
Fork 0
mirror of https://gitee.com/mateos/mateclaw.git synced 2026-09-15 11:58:34 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

docs(webchat): clarify agentId is pinned at conversation creation

Browse Source 
The WebChat stream endpoint resolves agentId only when the
(visitorId + sessionId) conversation is first created; later requests
with a different agentId reuse the existing conversation's agent and
silently ignore the new value. Document this on WebChatRequest.agentId
so integrators know to use a new sessionId to reach another agent.
This commit is contained in:
倪程伟 2026-06-09 10:40:26 +08:00 committed by matevip
parent a40868eff2
commit 12c24651a2
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
mateclaw-server/src/main/java/vip/mate/channel/webchat/WebChatController.java
View File

@ -328,7 +328,10 @@ public class WebChatController {
private String message; private String message;
private String visitorId; private String visitorId;
/** Optional: route this call to a specific agent instead of the channel's bound agent. /** Optional: route this call to a specific agent instead of the channel's bound agent.
* Must belong to the channel's workspace. */ * Must belong to the channel's workspace.
* <p>Only applied when the (visitorId + sessionId) conversation is first created. Once that
* conversation exists, its agent is fixed: a different agentId on later requests is silently
* ignored. To talk to another agent, use a new sessionId (or a new visitorId). */
private Long agentId; private Long agentId;
/** Optional: open a distinct conversation thread for the same visitor. /** Optional: open a distinct conversation thread for the same visitor.
* Composed into the server-derived conversationId; never used as a raw conversationId. */ * Composed into the server-derived conversationId; never used as a raw conversationId. */