Description
Telegram-Bridge fails to start with a TELGRAM_BOT_TOKEN environment variable defined. Only once SANDBOX_NAME is set, will telegram-bridge starts.
Reproduction Steps
- Set environment variable TELEGRAM_BOT_TOKEN=xxx:yyy
- Issue NemoClaw start
- telegram-bridge fails to go status: running in NemoClaw status
- set SANDBOX_NAME environment variable to sandbox
- telegram-bridge starts immediately
user@spark01:~$ export TELEGRAM_BOT_TOKEN=xxx:yyy
user@spark01:~$ nemoclaw start
[services] telegram-bridge started (PID 3923247)
[services] cloudflared not found — no public URL. Install: brev-setup.sh or manually.
┌─────────────────────────────────────────────────────┐
│ NemoClaw Services │
│ │
│ Telegram: bridge running │
│ │
│ Run 'openshell term' to monitor egress approvals │
└─────────────────────────────────────────────────────┘
user@spark01:~$ nemoclaw status
Sandboxes:
research *
● telegram-bridge (stopped)
● cloudflared (stopped)
user@spark01:~$ export SANDBOX_NAME=research
user@spark01:~$ nemoclaw status
Sandboxes:
research *
● telegram-bridge (PID 3923247)
● cloudflared (stopped)Validate: unset SANDBOX_NAME & telegram-bridge immediately fails
user@spark01:~$ unset SANDBOX_NAME
user@spark01:~$ nemoclaw status
Sandboxes:
research *
● telegram-bridge (stopped)
● cloudflared (stopped)Environment
OS: Ubuntu 24.04.4 LTS
Platform: DGX Spark
NemoClaw Version: nemoclaw v0.1.0
Debug Output
Logs
Checklist
Description
Telegram-Bridge fails to start with a TELGRAM_BOT_TOKEN environment variable defined. Only once SANDBOX_NAME is set, will telegram-bridge starts.
Reproduction Steps
Validate: unset SANDBOX_NAME & telegram-bridge immediately fails
Environment
OS: Ubuntu 24.04.4 LTS
Platform: DGX Spark
NemoClaw Version: nemoclaw v0.1.0
Debug Output
Logs
Checklist