openclaw - 💡(How to fix) Fix [Feature]: Improve UX for connecting new channels (avoid onboarding flow for new channel or fix) [1 participants]

<img width="1920" height="919" alt="Image" src="https://github.com/user-attachments/assets/18d90a24-95a3-4839-9e71-259eb7b51cc1" />

Summary

Make it easy to add and manage channels directly from the dashboard without going through the onboarding flow.

Problem to solve

Currently, connecting new channels is confusing and overly complex. The process relies heavily on the onboarding flow, which is not intuitive and feels disconnected from normal usage.

Users struggle to understand:

where to add a new channel after setup how to reconfigure or update an existing channel what steps are required and in what order

The onboarding interface mixes multiple concerns (security, models, channels, tools), making it difficult to focus on just adding a channel. This creates friction and discourages usage.

Proposed solution

Introduce a dedicated and simplified channel management experience:

Add a "Channels" page in the dashboard Provide a clear "Add Channel" button Use a step-by-step guided flow (wizard) for each channel: Step 1: Select platform (Telegram, Discord, etc.) Step 2: Enter required credentials (token, keys, etc.) Step 3: Validate configuration in real time Step 4: Confirm and activate Allow users to: Edit existing channels easily See connection status (connected / error / pending) Retry or fix errors with clear feedback Remove the need to re-run onboarding for adding channels Reduce reliance on CLI for basic configuration

Alternatives considered

Keeping onboarding as the primary entry point → Rejected because onboarding is too heavy and not designed for incremental configuration Improving documentation only → Not sufficient; the issue is UX complexity, not lack of instructions

Impact

Affected users: All users, especially new users and non-technical users Severity: High (blocks smooth setup and adoption) Frequency: Always when adding or modifying channels Consequence: Slower setup User confusion Increased risk of misconfiguration Reliance on trial-and-error and CLI

Evidence/examples

Users must go through onboarding even for simple channel additions Channel configuration is not discoverable in the UI Current flow mixes unrelated concerns, increasing cognitive load

Additional information

Improving this area would significantly enhance first-time user experience and reduce friction. Channel setup is a core feature and should be as simple and clear as possible.