Summary

openclaw status fails with:

channels.telegram.botToken: unresolved SecretRef "env:default:TELEGRAM_BOT_TOKEN"

…even when the Telegram channel is healthy and openclaw doctor reports Telegram: ok.

Environment

• OpenClaw: 2026.3.2 (85377a2)
• Host: Linux (systemd user service)
• Channel config includes:
  • channels.telegram.enabled: true
  • channels.telegram.botToken: "${TELEGRAM_BOT_TOKEN}"
• TELEGRAM_BOT_TOKEN exists in ~/.openclaw/.env and matches Telegram token format.

Repro

1. Set Telegram token via env SecretRef (${TELEGRAM_BOT_TOKEN})
2. Ensure gateway is running and Telegram is connected
3. Run:
   • openclaw doctor ✅ shows Telegram: ok (@...bot)
   • openclaw gateway status ✅ healthy
   • openclaw status ❌ fails with unresolved SecretRef error

Observed behavior

status appears to resolve SecretRef on a path that does not use the active resolved runtime snapshot, causing a false unresolved error for an active, healthy channel.

Expected behavior

openclaw status should either:

1. Use the active runtime snapshot (same effective data path as doctor), or
2. Fall back gracefully when runtime already has resolved secrets.

Notes

• openclaw secrets reload does not change outcome.
• openclaw secrets audit reports unresolved=0.
• This makes status unreliable as a health command in this configuration.