Telegram bridge status is mis-reported

[DanTup]

Description

Both times I've set this up, the telegram bridge status is not reported correctly. nemoclaw start starts the bridge, but status says it's not running, and nemoclaw stop always says it's not running (and therefore does not stop it).

Reproduction Steps

1. Set up nemoclaw
2. Run nemoclaw stop
3. Set up a telegram bot key in the env var
4. Run nemoclaw start and notice it says the bridge is running
5. Run nemoclaw status and notice it says it is not running
6. Run nemoclaw stop and notice that it does not stop the bridge, saying it's not running
7. Run ps and see the bridge is still running.

Environment

• OS: Ubuntu 24.04
• Node: v22.22.1
• Docker: 29.3.0, build 5927d80
• Nemoclaw: commit be7ec09 with fix: resolve openclaw.json permissions conflict and scope Dockerfile … #570 applied to get past onboarding (note: nemoclaw --version as the template asks for does not work, it says unknown command)

Debug Output

Logs

Checklist

• I confirmed this bug is reproducible
• I searched existing issues and this is not a duplicate

[wscurran]

✨ Thanks for submitting this issue with a detailed description and reproduction steps, it addresses a mis-reported Telegram bridge status, which could be related to the Telegram integration or status reporting mechanism.

---

Possibly related open PRs:

• #865 fix(security): add rate limiting to Telegram bridge
• #862 fix: auto-reset telegram bridge session after lock failure
• #860 fix: queue telegram bridge messages per chat to prevent session lock contention