openclaw - 💡(How to fix) Fix Feature request: per-message token/cost metadata in mobile app and channel surfaces [1 participants]

Summary

The Control UI (localhost:18789) already shows excellent per-message token/cost metadata beneath each assistant reply:

↑59 ↓13.4k R2.2M W43.9k 0% ctx claude-sonnet-4-6

This shows input tokens, output tokens, cache read/write, context window %, and model — and it turns yellow at 75% ctx and red at 90% ctx as a warning. It is genuinely excellent.

Request

Surface this same data (or a condensed version) in:

1. iOS/Android native chat view — even a subtle footer line per assistant message would be valuable
2. Channel surfaces (Signal, iMessage, Telegram, BlueBubbles, etc.) — as an optional footer appended to replies, ideally behind a user toggle/setting

Use Case

Users actively chatting via mobile or messaging channels have no visibility into context fill. They only discover the session is large when responses slow down or costs spike. Knowing the % ctx in real-time lets users decide when to /compact or start a fresh session — preventing runaway costs.

The Control UI implementation is already perfect. This is purely a request to extend that visibility to the surfaces where many users spend most of their time.

Workarounds Considered

• Portal widget polling session_status — works but not per-message
• Userscript injection — fragile across browser updates
• Native support would be far superior

Thanks for considering this!