NemoClaw failed adding Telegram channel

at step 10 of the playbook NemoClaw with Nemotron-3-Super and Telegram on DGX Spark | DGX Spark
nemoclaw start command does not prompt for API Key as expected!
instead it says Key is not set!

Hi raed.hijer,

Apologies for the confusion. Before running nemoclaw start, you can run:

export NVIDIA_API_KEY=<your key>

like you did for Telegram and it should go through. I’ll communicate internally to make this more clear. Please let me know if this works for you!

thanks for the tip @cyen1 running the export command above did make it run ok and generated bridge started/ Telegram : bridge running (as below screenshot) … but typing a text message at MyBot (on my phone) did not generate any response from the agent!
Is there any other setting/approval/or anything else I am missing?

image

Hi raed.hijer,

NemoClaw has gotten a few updates since this playbook was released. Can you try again with the latest version?

curl -fsSL https://www.nvidia.com/nemoclaw.sh | bash

The onboarding process should ask for your Telegram token and User ID. Once the sandbox is created, try communicating with your bot again and let me know how it goes!

Why is an NVIDIA key needed? Works fine without it (except groups which are broken upstream)

If you’re not using NVIDIA inference for Telegram, you can just put a dummy value. Otherwise, an NVIDIA key would be necessary. The new onboarding process should look a little different to what’s in the playbook right now, so I’d encourage you to try that. The playbook should still apply to v0.0.4, but stay tuned for future playbooks.

1 Like

Thank you for the clarification!
And telegram groups work again on OC2026.04.10/OS0.0.26/NC0.0.13