marketing-shibata50/multica
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: clarify channel route key conversation binding

Browse source
This commit is contained in:
Jiayuan Zhang 2026-02-17 03:15:37 +08:00
parent dee70ea659
commit c4d9f0273a
1 changed files with 6 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/development.md
View file

@ -75,6 +75,12 @@ Telegram behavior:
- `/session <id>` switches the active conversation.
- `/sessions` lists available conversations.
Channel route behavior:
- Runtime route key is `channelId:accountId:externalConversationId`.
- Each route key is bound to one Hub `conversationId`.
- Incoming/outgoing channel traffic is isolated per bound conversation (no global first-agent fallback).
## Local Full-Stack Notes (`pnpm dev:local`)
`pnpm dev:local` is the recommended way to run the full local stack for integration work.