Description
Summary
Telegram bot never starts. The credential placeholder is never resolved to the actual bot token inside the sandbox environment.
Expected Result
TELEGRAM_BOT_TOKEN=8515537511:AAG... (actual token value)
Actual Result
TELEGRAM_BOT_TOKEN=openshell:resolve:env:v17161140828352707040_TELEGRAM_BOT_TOKEN
Additional Evidence
- Bot token is valid — confirmed via
curl https://api.telegram.org/bot{token}/getMe returns correct bot info
- OpenClaw log shows "starting channels and sidecars..." followed immediately by gateway ready — no Telegram channel initialization, no errors
openshell provider get spark-nemo-telegram-bridge shows the provider is registered with TELEGRAM_BOT_TOKEN as a credential keyopenshell provider update spark-nemo-telegram-bridge --credential TELEGRAM_BOT_TOKEN=... does not fix it — placeholder hash changes but remains unresolved
Notes
Brave search (BRAVE_API_KEY) has the same unresolved placeholder but web_search works correctly via the L7 proxy rewrite. Telegram does not benefit from this proxy rewrite because the token appears in the URL path (/bot{token}/getUpdates) which requires the real value, not a placeholder.
v0.0.53 release notes mention "Telegram placeholder repair" but the fix does not appear to be effective on DGX Spark aarch64.
Related: #4251
Reproduction Steps
- Run
nemoclaw onboard with Telegram configured
- SSH into sandbox:
ssh openshell-spark-nemo
- Run
env | grep TELEGRAM
Environment
- NemoClaw: v0.0.53
- OpenClaw: 2026.5.22
- OpenShell: 0.0.44
- Hardware: NVIDIA DGX Spark Founders Edition (aarch64)
- Inference: Local vLLM (nemotron-3-super)
Debug Output
Logs
Checklist
Description
Summary
Telegram bot never starts. The credential placeholder is never resolved to the actual bot token inside the sandbox environment.
Expected Result
TELEGRAM_BOT_TOKEN=8515537511:AAG...(actual token value)Actual Result
TELEGRAM_BOT_TOKEN=openshell:resolve:env:v17161140828352707040_TELEGRAM_BOT_TOKENAdditional Evidence
curl https://api.telegram.org/bot{token}/getMereturns correct bot infoopenshell provider get spark-nemo-telegram-bridgeshows the provider is registered withTELEGRAM_BOT_TOKENas a credential keyopenshell provider update spark-nemo-telegram-bridge --credential TELEGRAM_BOT_TOKEN=...does not fix it — placeholder hash changes but remains unresolvedNotes
Brave search (BRAVE_API_KEY) has the same unresolved placeholder but web_search works correctly via the L7 proxy rewrite. Telegram does not benefit from this proxy rewrite because the token appears in the URL path (
/bot{token}/getUpdates) which requires the real value, not a placeholder.v0.0.53 release notes mention "Telegram placeholder repair" but the fix does not appear to be effective on DGX Spark aarch64.
Related: #4251
Reproduction Steps
nemoclaw onboardwith Telegram configuredssh openshell-spark-nemoenv | grep TELEGRAMEnvironment
Debug Output
Logs
Checklist