Skip to content

[Nemoclaw][All Platform]onboard skips messaging channel selection, but policy preset step still auto-selects messaging presets from stored credentials #1610

@zNeill

Description

@zNeill

Description

Description

When running nemoclaw onboard, if the user skips all messaging channels in the Messaging channels step, the later Policy presets step still auto-suggests and preselects messaging-related presets such as telegram, discord, and slack.

This appears to happen because preset suggestions are derived from detected credentials in the credential store / environment, rather than from the user’s current onboarding selections.

As a result, the onboarding flow behaves inconsistently:

  • Step 5 indicates messaging channels were skipped
  • Step 8 still suggests/applies messaging-related policy presets

This is confusing and makes it look like the previous step was ignored.

Reproduction Steps

  1. Ensure messaging credentials already exist in the host environment or credential store:
    • TELEGRAM_BOT_TOKEN
    • DISCORD_BOT_TOKEN
    • SLACK_BOT_TOKEN
  2. Run: nemoclaw onboard
  3. At [5/8] Messaging channels, do not select any channels and press Enter so the flow shows:
    • Skipping messaging channels.
  4. Continue onboarding until [8/8] Policy presets
  5. Observe that messaging-related presets are still suggested / preselected (for example discord, slack, telegram)

Actual Result

Even though messaging channels were skipped in the messaging step, the policy preset step still auto-selects or suggests messaging-related presets based on stored credentials.

Example observed behavior:

  • Messaging step:
    • Telegram / Discord / Slack shown as configured
    • User presses Enter without selecting any
    • Flow prints Skipping messaging channels.
  • Policy step later shows:
    • discord checked
    • slack checked
    • telegram checked

Expected Result

If the user skips messaging channels during onboarding, messaging-related policy presets should not be automatically suggested or preselected later in the same onboarding session.

At minimum, policy suggestions should reflect the current onboarding selection, not only previously detected credentials.

Suspected Cause

Policy presets suggestions are currently built from stored credentials / environment variables instead of the user’s current messaging choices in the same onboarding run.

Observed code path indicates suggestions are derived from checks like:

  • getCredential( TELEGRAM_BOT_TOKEN )
  • getCredential( SLACK_BOT_TOKEN ) || process.env.SLACK_BOT_TOKEN
  • getCredential( DISCORD_BOT_TOKEN ) || process.env.DISCORD_BOT_TOKEN

rather than from the selected messaging channels in the current onboard session.

Impact

  • Confusing onboarding UX
  • Makes it appear that the messaging selection step was ignored
  • Can cause users to unintentionally apply messaging-related network policies they did not intend to enable for this sandbox

Environment:- Platform: macos

  • NemoClaw: v0.0.9
  • OpenShell CLI: 0.0.24

Bug Details

Field Value
Priority Unprioritized
Action Dev - Open - To fix
Disposition Open issue
Module Machine Learning - NemoClaw
Keyword NemoClaw, NEMOCLAW_GH_SYNC_APPROVAL

[NVB# 6059818]

Metadata

Metadata

Assignees

No one assigned

    Labels

    Getting StartedUse this label to identify setup, installation, or onboarding issues.Integration: DiscordUse this label to identify Discord bot integration issues with NemoClaw.Integration: SlackUse this label to identify Slack integration issues with NemoClaw.Integration: TelegramUse this label to identify Telegram bot integration issues with NemoClaw.NV QABugs found by the NVIDIA QA TeamNemoClaw CLIUse this label to identify issues with the NemoClaw command-line interface (CLI).bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions