openclaw - 💡(How to fix) Fix [Bug] Wizard cross-overwrites credentials in multi-account plugins when "Add a new account" is selected [1 pull requests]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

When adding a new account for a channel (observed in wecom-openclaw-plugin and telegram), the wizard prompts "Bot ID / Token already configured. Keep it?" even if the user explicitly selected "Add a new account" with a unique Account ID.

Error Message

  1. Inconsistency: Built-in plugins like Telegram handle the "No" choice correctly, but external plugins using the accounts schema seem to trigger a file-write logic error where the wrong account's data is updated.

Root Cause

When adding a new account for a channel (observed in wecom-openclaw-plugin and telegram), the wizard prompts "Bot ID / Token already configured. Keep it?" even if the user explicitly selected "Add a new account" with a unique Account ID.

Fix Action

Fixed

RAW_BUFFERClick to expand / collapse

Version

v2026.5.6

Description

When adding a new account for a channel (observed in wecom-openclaw-plugin and telegram), the wizard prompts "Bot ID / Token already configured. Keep it?" even if the user explicitly selected "Add a new account" with a unique Account ID.

Key Issues Found

  1. UX Regression: Credentials from the main or existing account are pre-filled or checked globally, causing confusion for multi-agent setups.
  2. Configuration Corruption (Severe): In the WeCom plugin, after choosing "No" to the prompt and entering new credentials, the wizard mistakenly overwrote the botId of the existing main account in openclaw.json, instead of creating a new key under channels.wecom.accounts.
  3. Inconsistency: Built-in plugins like Telegram handle the "No" choice correctly, but external plugins using the accounts schema seem to trigger a file-write logic error where the wrong account's data is updated.

Reproduction Steps

  1. Have an existing wecom account configured.
  2. Run the wizard to configure wecom for a new Agent.
  3. Select Add a new account and enter a unique Account ID.
  4. When prompted "Bot ID already configured. Keep it?", select No.
  5. Enter new credentials for the new bot.
  6. Check openclaw.json and observe that accounts.main.botId has been overwritten with the new values instead of adding the new account.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug] Wizard cross-overwrites credentials in multi-account plugins when "Add a new account" is selected [1 pull requests]