[NemoClaw][Ubuntu 24.04.4 ][UX]:adding Telegram policy after onboarding does not clearly indicate that Telegram messaging is still disabled

[zNeill]

Description

Description

If a sandbox is created without enabling Telegram during nemoclaw onboard, adding the Telegram policy later does not enable Telegram messaging.

This is misleading from a user perspective because telegram appears as a normal policy preset / policy-add target, so it is easy to assume that applying the preset after sandbox creation should enable Telegram communication. In practice, the policy only opens egress to api.telegram.org. Telegram messaging still depends on onboarding-time provider creation, provider attachment, and channel configuration baked into the sandbox image.

As a result, users can believe they have enabled Telegram when they have only enabled network access.

Expected behavior

One of the following should happen:

• Adding the Telegram preset after onboarding enables Telegram end-to-end.
• Or the product clearly warns that policy changes alone do not enable Telegram and that rerunning nemoclaw onboard is required.

Actual behavior

• Sandbox is created without Telegram enabled during onboarding.
• Telegram policy is added later.
• Telegram messaging still does not work.
• The product does not make this distinction obvious at the point where the user applies the policy.

Repro steps

1. Run nemoclaw onboard.
2. Do not enable Telegram in the messaging channels step.
3. Let the sandbox finish creating.
4. After the sandbox is running, add the Telegram policy via preset / policy-add flow.
5. Attempt to communicate through Telegram.
6. Observe that Telegram messaging is still unavailable.

Impact

• Misleading post-onboarding experience
• Easy to misinterpret as broken Telegram integration
• Users may waste time debugging tokens or policy when the real issue is missing onboarding-time channel setup

Suggested fix

• Add an explicit warning when Telegram policy is applied to a sandbox that was not onboarded with Telegram enabled.
• Clarify in policy-related UX and docs that the Telegram preset only allows network egress and does not enable the channel integration by itself.
• Consider a dedicated post-onboarding enable flow for Telegram that rebuilds the required provider attachment and channel configuration automatically.

Environment

OS: Ubuntu 24.04.4 LTS

NemoClaw: v0.0.10-9-gc4767b63

OpenShell Cluster: v0.0.25

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# 6063335]