Skip to content

openclaw-weixin plugin v2.4.4 + OpenClaw 2026.6.1: Channel shows OFF / not configured, startAccount never called #91129

Description

@xuanyyang

ISSUE REPORT: openclaw-weixin plugin 鈥?Gateway shows channel "OFF / not configured", startAccount never called

Environment

Item Value
OS Windows 11 (10.0.26200)
Node.js v24.16.0
OpenClaw 2026.6.1 (2e08f0f)
@tencent-weixin/openclaw-weixin 2.4.4 (npm installed, latest)
Claude Code CLI 2.1.168 (logged in, works non-interactively)

Symptoms

  1. Plugin installs and loads successfully. Gateway logs show:

    [plugins] loading openclaw-weixin from .../dist/index.js
    gateway/channels/openclaw-weixin [compat] Host OpenClaw 2026.6.1 >= 2026.3.22, OK.
    gateway: auto-enabled plugins for this runtime without writing config:
      - openclaw-weixin configured, enabled automatically.
    
  2. startAccount() is never called. No sign of startAccount entry, starting weixin webhook, or monitorWeixinProvider anywhere in the logs. Only [compat] lines appear.

  3. QR code scan login succeeded. Token is saved to state:

    ~/.openclaw/state/openclaw-weixin/accounts/ad6e0a00b087-im-bot.json
    -> token: present, baseUrl: https://ilinkai.weixin.qq.com, configured: true
    
  4. openclaw status --deep shows:

    openclaw-weixin 鈹?OFF 鈹?not configured
    
  5. Agent routing binding is set:

    main <- openclaw-weixin accountId=ad6e0a00b087-im-bot
    

Config

{
  "channels": {
    "openclaw-weixin": {
      "baseUrl": "https://ilinkai.weixin.qq.com",
      "accounts": {
        "ad6e0a00b087-im-bot": { "enabled": true }
      }
    }
  },
  "agents": {
    "defaults": {
      "model": {
        "primary": "anthropic/claude-opus-4-8",
        "fallbacks": ["anthropic/claude-sonnet-4-6"]
      }
    }
  }
}

Troubleshooting attempted

  • openclaw doctor --fix 鈥?applied fixes, no change
  • openclaw agents bind --bind "openclaw-weixin:ad6e0a00b087-im-bot" 鈥?binding successful, still "not configured"
  • Set OPENCLAW_STATE_DIR and OPENCLAW_CONFIG env vars 鈥?no change
  • Added accounts.default entry 鈥?no change
  • Rebuilt gateway install from scratch 鈥?no change
  • Gateway started with DEBUG log level 鈥?weixin plugin only emits [compat] lines, nothing else
  • DNS issues resolved via dns.setServers + preload script (API reachable, QR login worked)
  • Official npx @tencent-weixin/openclaw-weixin-cli install tried 鈥?same result

Suspected root cause

Likely related to known issues:

Expected behavior

After Gateway starts, startAccount() should be called, launching the monitorWeixinProvider long-poll loop. Logs should contain "starting weixin webhook". openclaw status --deep should show openclaw-weixin 鈹?ON 鈹?running.

Relevant Gateway logs (startup section, DEBUG level)

[gateway] loading configuration鈥?[gateway] resolving authentication鈥?[gateway] starting...
[gateway] auto-enabled plugins: - openclaw-weixin configured, enabled automatically.
[gateway] starting HTTP server...
[health-monitor] started (interval: 300s)
[plugins] plugins.allow is empty; discovered non-bundled plugins may auto-load: openclaw-weixin
[plugins] loading openclaw-weixin from .../dist/index.js
[plugins] loaded 9 plugin(s) (9 attempted)
[gateway] agent model: anthropic/claude-opus-4-8
[gateway] http server listening (9 plugins: ..., openclaw-weixin, ...)
[gateway] starting channels and sidecars...
[gateway] ready
[heartbeat] started
// <- No weixin channel logs appear beyond this point

Metadata

Metadata

Assignees

No one assigned

    Labels

    P1High-priority user-facing bug, regression, or broken workflow.clawsweeper:needs-live-reproClawSweeper needs live local, crabbox, or manual validation to confirm this issue.clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.clawsweeper:needs-product-decisionClawSweeper marked this issue as needing a product or behavior decision.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.impact:message-lossChannel message delivery can be lost, duplicated, or misrouted.impact:session-stateSession, memory, transcript, context, or agent state can drift or corrupt.issue-rating: 🐚 platinum hermitGood issue quality with a plausible reproduction path needing some confirmation.staleMarked as stale due to inactivity

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions