Problem
The onboarding Channels step requires at least one of the following token-based channels:
It does not recognize an already-installed, enabled, and linked Signal channel.
This makes a Signal-only deployment unable to complete onboarding without creating an unrelated throwaway channel/token.
Reproduction
- Use AlphaClaw
0.9.34 with its matching OpenClaw version.
- Install and enable the OpenClaw Signal plugin.
- Configure
channels.signal.enabled: true with its linked signal-cli state and account.
- Start AlphaClaw and open the setup wizard.
- Reach the Channels step.
The wizard reports that a channel is required and offers only Telegram, Discord, and Slack. It does not show Signal or consider the configured Signal channel valid.
Cause
lib/public/js/components/onboarding/welcome-config.js checks only TELEGRAM_BOT_TOKEN, DISCORD_BOT_TOKEN, SLACK_BOT_TOKEN, and SLACK_APP_TOKEN in getChannelsGroupError. The channel accordion is similarly hard-coded to those three channels.
Expected behavior
A configured Signal channel should satisfy the onboarding requirement. Ideally the Channels step would show Signal as Configured (without requiring a token), or allow the wizard to continue when the backend reports that Signal is enabled and linked.
Why this matters
Signal is a reasonable single-owner/control channel for a private agent. Requiring an unrelated channel introduces unnecessary credentials, attack surface, and cleanup work solely to pass onboarding.
Problem
The onboarding Channels step requires at least one of the following token-based channels:
It does not recognize an already-installed, enabled, and linked Signal channel.
This makes a Signal-only deployment unable to complete onboarding without creating an unrelated throwaway channel/token.
Reproduction
0.9.34with its matching OpenClaw version.channels.signal.enabled: truewith its linkedsignal-clistate and account.The wizard reports that a channel is required and offers only Telegram, Discord, and Slack. It does not show Signal or consider the configured Signal channel valid.
Cause
lib/public/js/components/onboarding/welcome-config.jschecks onlyTELEGRAM_BOT_TOKEN,DISCORD_BOT_TOKEN,SLACK_BOT_TOKEN, andSLACK_APP_TOKENingetChannelsGroupError. The channel accordion is similarly hard-coded to those three channels.Expected behavior
A configured Signal channel should satisfy the onboarding requirement. Ideally the Channels step would show Signal as
Configured(without requiring a token), or allow the wizard to continue when the backend reports that Signal is enabled and linked.Why this matters
Signal is a reasonable single-owner/control channel for a private agent. Requiring an unrelated channel introduces unnecessary credentials, attack surface, and cleanup work solely to pass onboarding.