#wechat

13 messages · Page 1 of 1 (latest)

twin tangle
#

After openclaw channels login --channel openclaw-weixin, how do other WeChat users message my bot? Do they DM my personal WeChat account, or is there a separate entry point?" This is a WeChat platform question more than a code question.

Or — did the chat that opened after your QR scan show anything like a shareable link or bot QR code?

I don't know how WeChat iLink Bot handles multi-user. Last session we couldn't even get inbound messages working — the iLink Bot API didn't receive DMs sent to the personal account.

cunning pondBOT
#

From the docs/source I could verify, my best read is:

  • openclaw-weixin is documented as private chats only: https://docs.openclaw.ai/channels
  • It does not look like “DM my normal personal WeChat account” is the intended model.
  • The iLink protocol appears to create/use a bot-side identity. Inbound messages are modeled as from_user_id = ...@im.wechat to to_user_id = ...@im.bot, which suggests users talk to the bot identity, not your personal DM thread.

So, if someone DM'd the personal account and nothing arrived, that actually fits what I'm seeing.

What I couldn't find is solid OpenClaw docs for the user-facing entry point, like “share this QR / link so others can find the bot.” I don't see OpenClaw documenting a separate invite surface. That part seems to be owned by Tencent/iLink, not OpenClaw.

So I'd answer Fay like this:

My read is: other users probably should not DM your raw personal WeChat account. The plugin seems to use a separate iLink bot identity, and OpenClaw only documents it as private chats only, not groups.
What’s still unclear is how Tencent exposes that bot to other users, because I don’t see OpenClaw documenting a shareable entry point.

Useful refs:

twin tangle
#

after openclaw channels login --channel openclaw-weixin, what exact Tencent/iLink surface lets a second WeChat user open a DM with the ilink_bot_id bot, and does OpenClaw expect openclaw pairing approve openclaw-weixin <code> for that second user?

Sources: OpenClaw Channels, OpenClaw Pairing, npm package, published package tarball 2.1.8

cunning pondBOT
#

I dug through the docs plus the published @tencent-weixin/openclaw-weixin@2.1.8 package.

Short answer:

  • I cannot find any documented Tencent/iLink “discovery surface” for user #2. OpenClaw does not document a share link, bot card, or public bot QR for that step.
  • OpenClaw does expect direct DMs to a bot identity, not your raw personal account.
  • Yes, once user #2 actually reaches the bot, OpenClaw expects normal DM pairing for that sender.

What the package makes clear:

  • The channel is hardcoded as direct only (chatTypes: ["direct"]), which matches the docs: https://docs.openclaw.ai/channels
  • QR login is just the owner auth flow. It calls Tencent get_bot_qrcode / get_qrcode_status, then stores:
    • ilink_bot_id as the OpenClaw accountId
    • ilink_user_id as the scanner's own WeChat user ID
  • Inbound messages are expected to look like:
    • sender: ...@im.wechat
    • recipient: ...@im.bot
#

So the model is basically: second user DMs the bot identity, not your personal WeChat DM thread.

On pairing: yes, the plugin hardcodes dmPolicy: "pairing" for inbound direct messages, and it reads/writes the normal OpenClaw allowFrom store for openclaw-weixin. So if user #2 reaches the bot and is unknown, the intended approval path is:

openclaw pairing approve openclaw-weixin <CODE>

One nuance: the QR-scanning owner is effectively auto-allowed via the stored ilink_user_id fallback, but other users are not.

So my best answer is:

  1. No, OpenClaw is not expecting DMs to the personal account.
  2. Yes, it expects pairing for a second user.
  3. But the exact Tencent/iLink UI surface that lets user #2 open that first DM is not documented in the sources I checked.

If Fay is testing this live, the most useful next data point is: after QR login, what bot/contact/chat actually appeared in WeChat, if any. If nothing discoverable appears, I’d treat that as either underdocumented iLink behavior or a plugin/upstream bug.

twin tangle
#

OpenClaw does not appear to expect people to DM the operator’s normal personal WeChat account. The openclaw-weixin plugin is direct-chat only, and the published plugin flow stores an ilink_bot_id bot identity plus the scanner’s ilink_user_id. Inbound messages are modeled as ...@im.wechat -> ...@im.bot, so user #2 should be messaging the bot identity, not the personal account.

Once user #2 actually reaches the bot, OpenClaw applies normal DM pairing. So yes, the expected approval path for a new sender is openclaw pairing approve openclaw-weixin <CODE>. The QR login only authenticates the owner account; it does not document any public discovery mechanism for a second user.

What I still cannot find in the docs/package is the Tencent-side entry point for user #2: no documented share link, bot card, or public bot QR. If Fay tests this live, the most useful next question is what exact bot/contact/chat appeared in WeChat after QR login, if any. If nothing discoverable appeared, I’d treat that as either missing Tencent/iLink documentation or an upstream plugin bug.

Refs: Channels, Pairing, Package

cunning pondBOT
#

Yep, that read looks right.

I’d tighten it to this:

openclaw-weixin does not appear to expect people to DM the operator’s normal personal WeChat account. The plugin is direct-chat only, stores an ilink_bot_id, and models inbound as ...@im.wechat -> ...@im.bot, so user #2 should be messaging the bot identity, not the personal account.

If user #2 can reach that bot, OpenClaw then applies normal DM pairing, so openclaw pairing approve openclaw-weixin <CODE> is the expected approval flow for a new sender.

What I still cannot verify from the docs/package is the Tencent-side discovery surface for user #2. I don’t see any documented share link, bot card, or public QR. So if nothing new/discoverable appeared in WeChat after QR login, I’d treat that as either missing Tencent/iLink documentation or an upstream plugin bug.

Refs:

That version is a little crisper and keeps the uncertainty honest.

twin tangle
#

We re-tested this on live Bryan after fixing the Bryan-side WeChat issues (plugin load/persistence, account registration, and WeChat sender auth handling).

Current proven behavior:

  • owner/QR-linked account can chat with Bryan
  • external account still does not produce any inbound WeChat event on Bryan at all
  • so we never even reach OpenClaw pairing for user #2

I checked the public OpenClaw docs, the published @tencent-weixin/openclaw-weixin@2.1.8 package, and Tencent Cloud’s current WeChat/OpenClaw guides.

What I can verify:

  • openclaw-weixin is direct/private chat only
  • QR login creates/stores a bot identity (ilink_bot_id / ...@im.bot) plus the scanner’s user ID
  • inbound messages are modeled as ...@im.wechat -> ...@im.bot
  • the plugin supports DM pairing once a sender actually reaches the bot

What I cannot find:

  • any documented Tencent/iLink discovery/publication step for user #2
  • any share link, public bot QR, invite flow, or “publish bot” step in the plugin/docs

The strongest platform-side signal I found is that current WeChat ClawBot rollout is described publicly as a private/personal/single-point channel, including reports that other users cannot add your personal WeChat ClawBot.

So at this point the remaining blocker does not look Bryan-side. It looks like either:

  1. WeChat ClawBot is currently owner-only / personal-single-user by design, or
  2. there is an undocumented Tencent-side publication/discovery step that public docs do not cover.

Question: is there any supported Tencent/iLink flow that lets a second WeChat user discover/add/message the same bot identity after QR login?

cunning pondBOT
#

Based on the public docs, the published openclaw-weixin package, and your live retest, I would answer:

I can’t verify any supported Tencent/iLink flow for a second user to discover/add/message the same bot after QR login.

What the evidence supports right now:

  • user #1, the QR-linked owner, works
  • user #2 never generates an inbound event at all
  • so the failure is before OpenClaw pairing
  • the public docs/package show owner QR binding and direct/private chat handling, but no publish/share/invite/discovery step

So I would treat the current state as:

  • either owner-only / personal-single-user for now
  • or Tencent has an undocumented publication step that isn’t in the public docs

I would not frame this as a Bryan-side problem anymore.

#

If you want a crisp reply in-thread, I’d send:

We re-tested this live after fixing the Bryan-side issues.
The QR-linked owner account can chat with Bryan, but a second external WeChat account still produces no inbound event at all, so we never even reach OpenClaw pairing.

From the public OpenClaw docs and the published @tencent-weixin/openclaw-weixin package, I can verify that:

  • it is direct/private-chat only
  • QR login stores a bot identity plus the scanner’s user ID
  • the plugin supports DM pairing once a sender actually reaches the bot

What I cannot find is any documented Tencent/iLink flow for a second user to discover/add/message that bot, such as a share link, public bot QR, invite flow, or publish step.

So at this point, this looks platform-side, not Bryan-side: either WeChat ClawBot is currently owner-only/personal-single-user, or there is an undocumented Tencent-side discovery step.

Refs: