@ycodium-ai/plugin-im 0.2.2966 → 0.2.2972

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -35,6 +35,12 @@ they pick their own project:
35
35
  `/repo` switches the project: the old thread is kept (still under that
36
36
  project's `/sessions`), the chat forgets it, and a running turn blocks the
37
37
  switch. The panel has a Pick project button.
38
+ - On Telegram a forum topic is a chat of its own: its chat id is `chat:topic`
39
+ (`chatIdOf`, only when Telegram marks the message `is_topic_message`; a reply
40
+ chain in an ordinary supergroup also carries `message_thread_id` and stays the
41
+ group), so each topic picks its own project and keeps its own thread. Sends to a
42
+ topic carry `message_thread_id`; edits, reactions and the member count use the
43
+ group id. General is the group itself.
38
44
  - A chat only hears the project it picked: one conclusion per finished turn and
39
45
  thread failures go to the chats that picked that project; a chat with no
40
46
  project hears nothing.
@@ -58,11 +64,13 @@ they pick their own project:
58
64
  Platforms are adapters behind one plugin, not three plugins. Lark uses the
59
65
  vendor SDK for its long connection; WeCom speaks JSON over a WebSocket; Telegram
60
66
  is HTTP long-polling. **WeCom App** (`wecom-app`) is the self-built application
61
- channel (YCO-235): HTTP callbacks with official encrypt/decrypt, URL verification,
62
- inbound text, and outbound `cgi-bin/message/send`. It listens on `127.0.0.1:30987`
63
- by default (path `/wecom-app-callback/<rowId>/<secret>`); put a reverse proxy or
64
- tunnel in front and paste the public URL into WeCom “Receive messages → API receive”.
65
- Streaming and media are not in this skeleton yet — final replies go out actively.
67
+ channel: HTTP callbacks with official encrypt/decrypt, URL verification, inbound
68
+ text and images (fetched through `media/get`), outbound text, images and files
69
+ (`media/upload` then `message/send`). Private chats only; group messages are ignored.
70
+ It listens on `127.0.0.1:30987` by default (path `/wecom-app-callback/<rowId>/<secret>`);
71
+ put a reverse proxy or tunnel in front and paste the public URL into WeCom “Receive
72
+ messages → API receive”. Each column is validated, and a row with problems does not
73
+ connect. Streaming replies are not done yet — final replies go out actively.
66
74
 
67
75
  The default is one message per finished turn. A single turn can produce dozens
68
76
  of assistant messages, mostly commentary between tool calls.