Back to Blog

Week of March 10: Better /status Links, Telegram-Native Media, and Stronger Delivery Reliability

Clearer /status URLs, broader Telegram-native message support, and reliability work across the stack.

DV

Dzianis Vashchuk

3 min read

This week was about making OpenClaw Box feel more like a native Telegram product and less like a narrow text wrapper around a runtime.

The visible improvements shipped in three layers at once:

  1. clearer user-facing links in /status
  2. much broader Telegram-native message support
  3. stronger proxy and gateway reliability around delivery and failure handling

/status is clearer now

The /status command now shows two explicitly labeled URLs:

  • Control Panel for tenant management
  • Browser for the cloud browser UI

This was a small copy change with a real usability payoff. Users no longer have to infer which URL is for settings and which one is for the browser surface.

OpenClaw now supports far more of Telegram's native message surface

This is the biggest product change of the week.

OpenClaw Box used to feel strongest on text, images, and voice. That was useful, but it was still narrower than how people naturally communicate in Telegram.

Now the bot handles a much broader range of native Telegram message types, including:

  • text
  • voice messages
  • audio files
  • photos
  • documents and uploaded files
  • videos
  • video notes
  • stickers
  • animations and GIFs
  • locations
  • contacts
  • venues

That means users can now send the kinds of things they already have in a real Telegram chat instead of converting everything into plain text first.

Telegram delivery moved closer to the right architecture

This week also pushed more Telegram delivery through the bot-to-gateway proxy path.

That matters because it moves the system away from brittle, bot-side special cases and closer to a cleaner model where the runtime receives the proper Telegram update path directly.

That architectural shift is less flashy than a UI launch, but it is the right foundation for a Telegram-native runtime product.

Reliability work shipped alongside the feature work

Several reliability changes landed around the same area:

  • more specific user-facing error messages instead of generic failures
  • transient replay for flaky gateway responses in isolated sessions
  • safer per-request user keys for media flows to reduce context pollution
  • stronger timeout classification and gateway health probing
  • continued work around media delivery and clip handling

These changes all push toward the same goal: when the user sends something in Telegram, the product should either handle it correctly or fail in a way that is explicit and actionable.

Why this week matters

If you zoom out, this week made OpenClaw Box more native in two senses.

It became more native to the Telegram platform by understanding more Telegram message types.

And it became more native to the tenant operating model by exposing the right URLs more clearly and hardening the path from user message to runtime delivery.

That is exactly the kind of progress we want:

  • less ceremony
  • fewer dead ends
  • more first-class behavior on the surfaces people actually use