feat(usage): ship built-in /usage full footer by Marvinthebored · Pull Request #92657 · openclaw/openclaw

Marvinthebored · 2026-06-13T11:21:44Z

Summary

Ship a built-in compact /usage full footer; users no longer need a JSON file for the pretty default.
Keep messages.usageTemplate as the advanced override path only. Inline/file templates replace the built-in when valid.
Remove the "default" sentinel and merge-over-default behavior. Strings are paths again.
Fall back to the built-in footer for unset, missing, invalid, or empty templates; explicit broken overrides emit an operator warning.
Document the template DSL and include the built-in footer as the custom-template starter block.
Preserve partial and total-only token reporting without inventing unknown split counts or false $0.0000 costs.

Real behavior proof

Behavior addressed: /usage full shows the built-in compact footer without any messages.usageTemplate JSON file.

Real environment tested: Real Telegram bot-to-bot group with a temp OpenClaw gateway started from this PR head, repo mock-openai, and a temp config that did not include messages.usageTemplate.

Exact steps or command run after this patch: Started scripts/e2e/mock-openai-server.mjs; started pnpm openclaw gateway --port 19947 with temp state/config; sent /usage full; sent @{sut} Please answer with OPENCLAW_E2E_OK only. through ~/.codex/skills/custom/telegram-e2e-bot-to-bot/scripts/probe.mjs.

Evidence after fix: Copied live output from the Telegram probe:

/usage full -> ⚙️ Usage footer: full.
@{sut} Please answer with OPENCLAW_E2E_OK only. -> OPENCLAW_E2E_OK
openai🤖 gpt5.5 🌑 🐌 | 📚 [⠐⠐⠐⠐⠐]128k ↕️ 11/7 🗄 0% 💰0.0000

Observed result after fix: Actual output showed the default footer in Telegram with no template file configured; mock OpenAI saw 1 request; command RTT 2437 ms; model-turn RTT 2536 ms.

What was not tested: No Telegram Desktop video artifact. Custom template replacement, broken-template warnings, empty-template fallback, partial token counts, total-only token counts, and total-only cost suppression are covered by focused tests, not by the live Telegram probe.

Verification

pnpm exec oxfmt --check src/auto-reply/reply/agent-runner.ts src/auto-reply/reply/agent-runner.misc.runreplyagent.test.ts src/auto-reply/usage-bar/contract.ts src/auto-reply/usage-bar/default-template.ts src/auto-reply/usage-bar/template.ts src/auto-reply/usage-bar/template.test.ts docs/concepts/usage-tracking.md
pnpm docs:list
pnpm check:docs
git diff --check
node scripts/run-vitest.mjs src/auto-reply/usage-bar/template.test.ts src/auto-reply/usage-bar/translator.test.ts test/vitest-scoped-config.test.ts src/auto-reply/reply/agent-runner.misc.runreplyagent.test.ts
Telegram bot-to-bot proof described above
.agents/skills/autoreview/scripts/autoreview --mode branch --base origin/main clean: no accepted/actionable findings

clawsweeper · 2026-06-13T11:23:41Z

Codex review: needs changes before merge. Reviewed June 13, 2026, 9:43 AM ET / 13:43 UTC.

Summary
Adds a built-in source template for /usage full, makes unset or unusable messages.usageTemplate fall back to it, updates usage contract/tests, and documents template authoring.

PR surface: Source +172, Tests +94, Docs +178. Total +444 across 7 files.

Reproducibility: not applicable. as a bug repro: this is a feature PR. Source inspection plus the PR body's live Telegram output give a high-confidence path showing the new footer behavior after the patch.

Review metrics: 1 noteworthy metric.

Config/default behavior: 1 changed fallback/default, 0 config keys added or removed. The PR changes how an existing config absence or invalid messages.usageTemplate renders for upgraded users, which needs maintainer acceptance before merge.

Stored data model
Persistent data-model change detected: persistent cache schema: src/auto-reply/reply/agent-runner.misc.runreplyagent.test.ts. Confirm migration or upgrade compatibility proof before merge.

Merge readiness
Overall: 🐚 platinum hermit
Proof: 🦞 diamond lobster
Patch quality: 🐚 platinum hermit
Result: ready for maintainer review.

Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch.

Rank-up moves:

Replace or qualify the unsupported limits.windows docs example.
[P2] Record maintainer acceptance of the new compact footer as the default /usage full output before merge.

Mantis proof suggestion
A native Telegram Desktop capture would complement the supplied live text output by showing the footer as users see it in chat. A maintainer can ask Mantis to capture proof by posting a new PR comment that starts with the OpenClaw Mantis account mention, followed by:

telegram desktop proof: verify /usage full with no messages.usageTemplate renders the built-in compact footer in Telegram.

Risk before merge

[P1] Merging intentionally changes default /usage full output for existing users with no valid messages.usageTemplate, replacing the legacy Usage: line and session-key suffix with the compact footer.

Maintainer options:

Fix Docs And Accept The New Default (recommended)
Replace or qualify the unsupported limits.windows example, then have maintainers explicitly accept the compact footer as the new /usage full default.
Keep Legacy Output As Default
Change the PR so unset or broken templates keep the legacy full footer and expose the compact template only through an explicit opt-in path.
Pause For The Broader Footer Contract
If maintainers want messages.responseFooter or inherited response-usage defaults decided first, pause this focused PR in favor of that product decision.

Next step before merge

[P2] A narrow automated repair can fix the unsupported docs example; maintainer acceptance of the default-output compatibility change remains separate.

Security
Cleared: The diff adds static template data, docs, and tests without new dependencies, workflow permissions, secret handling, package resolution, or executable template code.

Review findings

[P3] Use a contract-backed example for each — docs/concepts/usage-tracking.md:201

Review details

Best possible solution:

Land after replacing the unsupported docs example and after maintainers explicitly accept the default-output compatibility change.

Do we have a high-confidence way to reproduce the issue?

Not applicable as a bug repro: this is a feature PR. Source inspection plus the PR body's live Telegram output give a high-confidence path showing the new footer behavior after the patch.

Is this the best way to solve the issue?

Yes, with a small docs repair and explicit maintainer acceptance. The source-defined default template is a narrow path that preserves valid custom template replacement without adding a new config key.

Full review comments:

[P3] Use a contract-backed example for each — docs/concepts/usage-tracking.md:201
The piece-form docs show each: "limits.windows", but this page says provider rate-limit windows are not in the contract and buildUsageContract does not expose limits. Readers copying this snippet will render nothing, so replace it with a current contract-backed example, remove it, or mark it as generic/future-only syntax.
Confidence: 0.87

Overall correctness: patch is correct
Overall confidence: 0.87

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 27e24ca68325.

Label changes

Label changes:

add proof: sufficient: Contributor real behavior proof is sufficient. The PR body includes after-fix live Telegram bot-to-bot output from a temp gateway showing /usage full and the compact footer without a configured template.

Label justifications:

P2: This is a normal-priority user-facing usage-footer improvement with bounded blast radius and no urgent production regression.
merge-risk: 🚨 compatibility: The PR changes the default /usage full footer format and fallback behavior for existing sessions/configs without a valid custom template.
rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🦞 diamond lobster and patch quality is 🐚 platinum hermit.
status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Sufficient (live_output): The PR body includes after-fix live Telegram bot-to-bot output from a temp gateway showing /usage full and the compact footer without a configured template.
proof: sufficient: Contributor real behavior proof is sufficient. The PR body includes after-fix live Telegram bot-to-bot output from a temp gateway showing /usage full and the compact footer without a configured template.
mantis: telegram-visible-proof: Mantis should capture Telegram visible proof. The PR changes visible Telegram /usage full footer output, which a short Telegram Desktop recording can demonstrate clearly.

Evidence reviewed

PR surface:

Source +172, Tests +94, Docs +178. Total +444 across 7 files.

View PR surface stats

Area	Files	Added	Removed	Net
Source	4	195	23	+172
Tests	2	112	18	+94
Docs	1	183	5	+178
Config	0	0	0	0
Generated	0	0	0	0
Other	0	0	0	0
Total	7	490	46	+444

Acceptance criteria:

[P1] git diff --check.
[P1] pnpm check:docs.
[P1] pnpm exec oxfmt --check docs/concepts/usage-tracking.md.

What I checked:

Current main behavior: Current main returns undefined when messages.usageTemplate is unset or unusable, so /usage full stays on the legacy formatter unless a valid custom template is configured. (src/auto-reply/usage-bar/template.ts:64, 27e24ca68325)
PR head behavior: PR head changes loadUsageBarTemplate to return DEFAULT_USAGE_BAR_TEMPLATE when the config is unset or an inline/file template is unusable. (src/auto-reply/usage-bar/template.ts:150, 071c82355309)
Built-in template surface: The added default template renders provider/model, reasoning, fast/slow state, context, token counts, cache percentage, and cost when those contract fields are present. (src/auto-reply/usage-bar/default-template.ts:27, 071c82355309)
Docs finding evidence: The PR docs still show each: "limits.windows" even though the same PR docs state provider rate-limit windows are not in the contract. Public docs: docs/concepts/usage-tracking.md. (docs/concepts/usage-tracking.md:201, 071c82355309)
Real behavior proof: The PR body provides copied live output from a real Telegram bot-to-bot group and temp gateway showing /usage full plus a model turn with the compact footer and no configured template. (071c82355309)
Feature history: The current template renderer was introduced by 64d0fc83364e, then recently tightened by b477bfe84b and ff6940036b, which makes this PR a follow-up on the same usage-footer surface. (src/auto-reply/usage-bar/template.ts:1, 64d0fc83364e)

Likely related people:

Peetiegonzalez: Authored the merged native usage-template renderer and much of the current usage-bar contract/loader path that this PR extends. (role: feature history contributor; confidence: high; commits: 64d0fc83364e, 069cb8d63687, 8cc5d2d85c87; files: src/auto-reply/usage-bar/template.ts, src/auto-reply/usage-bar/translator.ts, src/auto-reply/usage-bar/contract.ts)
obviyus: Recently tightened usage-template fallback/reload behavior on current main and is assigned to this PR. (role: recent area contributor and assignee; confidence: high; commits: b477bfe84bf8, ff6940036b43; files: src/auto-reply/usage-bar/template.ts, src/auto-reply/usage-bar/template.test.ts, docs/concepts/usage-tracking.md)
Marvinthebored: Opened the merged native templated footer PR and this PR continues the same usage-footer authoring surface, beyond merely proposing the current branch. (role: feature proposer with merged domain history; confidence: medium; commits: ff6940036b43; files: src/auto-reply/usage-bar/template.ts, docs/concepts/usage-tracking.md)

What the crustacean ranks mean

🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

How this review workflow works

ClawSweeper keeps one durable marker-backed review comment per issue or PR.
Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
Maintainers can also comment @clawsweeper review to request a fresh review only.
Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

Set messages.usageTemplate to the sentinel "default" to render a good-looking built-in /usage full footer without supplying a template. Intentionally undocumented in the config schema/help for now; a path or inline object still overrides, and unset keeps the built-in line. The default lives in source (default-template.ts) rather than a shipped JSON so it stays in lockstep with the renderer. It keeps the 📚 context-window bar; it does not render limits/reset windows (the merged PluginHookReplyUsageState carries no limits data). Co-Authored-By: Claude Opus 4.8 <[email protected]>

… scale palette + docs - messages.usageTemplate now layers OVER the built-in default (objects merge by key, arrays/scalars replace), like other openclaw config objects, so a user template only needs the delta it adds/changes. - Default ships the full scale palette (braille/block/shade/moon/level/ weather/plants/moons6); users add more by name. - Document the template format end to end (the "default" sentinel, merge behavior, the contract paths, verb table, piece forms, a worked example) in docs/concepts/usage-tracking.md — previously unauthorable from docs. Co-Authored-By: Claude Opus 4.8 <[email protected]>

obviyus · 2026-06-13T13:46:42Z

Landed via rebase onto main.

Scoped tests:
- pnpm exec oxfmt --check src/auto-reply/reply/agent-runner.ts src/auto-reply/reply/agent-runner.misc.runreplyagent.test.ts src/auto-reply/usage-bar/contract.ts src/auto-reply/usage-bar/default-template.ts src/auto-reply/usage-bar/template.ts src/auto-reply/usage-bar/template.test.ts docs/concepts/usage-tracking.md
- node scripts/run-vitest.mjs src/auto-reply/usage-bar/template.test.ts src/auto-reply/usage-bar/translator.test.ts test/vitest-scoped-config.test.ts src/auto-reply/reply/agent-runner.misc.runreplyagent.test.ts
- pnpm check:docs
- git diff --check
- .agents/skills/autoreview/scripts/autoreview --mode branch --base origin/main
CI: green on final pushed SHA 071c823553090beac98bde580edd5abd30716bf5.
Changelog: not updated; release generation owns CHANGELOG.md, and the PR body carries release-note context.
Land commit: 071c823553090beac98bde580edd5abd30716bf5
Merge commit: 799488086414fd105c8287becd1c47a226f64d3b

Thanks @Marvinthebored!

The built-in default footer (added in openclaw#92657) only defined a `discord` surface. Telegram and every other surface fall through to `output.default`, which was authored for a wide terminal: space-separated badges, a leading space-less join onto the message body, and ↕️ token + 🗄 cache% segments. On a narrow Telegram screen this wrapped at arbitrary spaces (often mid-meter or between 📚 and its bar) and welded onto the end of the message text. Make `default` read well on a phone: - Leading \n so the footer sits on its own line below the body. - Tight badges (no separators between model/flags/reasoning/fast). - NBSP before "|" and 💰; 📚 glued hard to the meter so it can't wrap there. - Single regular space after "|" as the only sanctioned wrap point. - Drop ↕️ tokens and 🗄 cache% from the default — noise for most users (still available to anyone via a custom messages.usageTemplate). Discord surface trimmed to match for consistency (keeps its -# dim header).

…26.6.8) (#1144) This PR contains the following updates: | Package | Update | Change | |---|---|---| | [ghcr.io/openclaw/openclaw](https://openclaw.ai) ([source](https://github.com/openclaw/openclaw)) | patch | `2026.6.6` → `2026.6.8` | --- ### Release Notes <details> <summary>openclaw/openclaw (ghcr.io/openclaw/openclaw)</summary> ### [`v2026.6.8`](https://github.com/openclaw/openclaw/blob/HEAD/CHANGELOG.md#202668) [Compare Source](openclaw/openclaw@v2026.6.6...v2026.6.8) ##### Highlights - Telegram and WhatsApp channel delivery are richer and less brittle: Telegram can send structured rich text with tables, lists, expandable blockquotes, prompt-preserving CLI backend delivery, retired native draft migration, and safer rich-media boundaries, while WhatsApp now honors configured ACP bindings. ([#92679](openclaw/openclaw#92679), [#84082](openclaw/openclaw#84082), [#89421](openclaw/openclaw#89421), [#92513](openclaw/openclaw#92513)) Thanks [@obviyus](https://github.com/obviyus), [@jzakirov](https://github.com/jzakirov), [@spacegeologist](https://github.com/spacegeologist), and [@TurboTheTurtle](https://github.com/TurboTheTurtle). - Agent and Gateway recovery is sharper across account-scoped DM sends, generated media completions, restart shutdown aborts, yielded subagent pauses, yielded cron media, heartbeat dedupe, session identity prompts, and unknown OpenAI agent selector rejection. ([#92788](openclaw/openclaw#92788), [#91246](openclaw/openclaw#91246), [#91357](openclaw/openclaw#91357), [#92631](openclaw/openclaw#92631), [#92146](openclaw/openclaw#92146), [#91287](openclaw/openclaw#91287), [#92468](openclaw/openclaw#92468), [#92510](openclaw/openclaw#92510)) Thanks [@yetval](https://github.com/yetval), [@TurboTheTurtle](https://github.com/TurboTheTurtle), [@ooiuuii](https://github.com/ooiuuii), [@openperf](https://github.com/openperf), [@IWhatsskill](https://github.com/IWhatsskill), [@ZengWen-DT](https://github.com/ZengWen-DT), and [@zhangguiping-xydt](https://github.com/zhangguiping-xydt). - Provider/model handling expands and tightens with GLM-5.2, Claude Haiku 4.5 catalog rows, OpenRouter and Google Vertex provider-prefix normalization, managed SecretRef auth, bounded model browse discovery, storeless OpenAI Responses replay gating, and Claude 4.5 Copilot tool-streaming safety. ([#92796](openclaw/openclaw#92796), [#90116](openclaw/openclaw#90116), [#92627](openclaw/openclaw#92627), [#91218](openclaw/openclaw#91218), [#90686](openclaw/openclaw#90686), [#92247](openclaw/openclaw#92247), [#90706](openclaw/openclaw#90706), [#75393](openclaw/openclaw#75393)) Thanks [@arkyu2077](https://github.com/arkyu2077), [@liuhao1024](https://github.com/liuhao1024), [@bymle](https://github.com/bymle), [@rohitjavvadi](https://github.com/rohitjavvadi), [@samson910022](https://github.com/samson910022), [@snowzlm](https://github.com/snowzlm), and [@Kailigithub](https://github.com/Kailigithub). - `/usage` and reply payload hooks now have a native full footer renderer, default template, fixed-decimal formatting, credential-aware limits, better partial-count handling, and warnings for broken templates instead of silent bad output. ([#92657](openclaw/openclaw#92657), [#89835](openclaw/openclaw#89835), [#89629](openclaw/openclaw#89629)) Thanks [@Marvinthebored](https://github.com/Marvinthebored). - UI and mobile flows are steadier: workspace files can collapse and start collapsed, WebChat backscroll survives streaming, the sidebar session picker remains interactive above the desktop workbench, reset soft args survive UI dispatch, stale dashboard session parent lineage is preserved, and iOS reconnects stale foreground gateways. ([#92779](openclaw/openclaw#92779), [#92622](openclaw/openclaw#92622), [#92705](openclaw/openclaw#92705), [#91353](openclaw/openclaw#91353), [#90658](openclaw/openclaw#90658), [#92552](openclaw/openclaw#92552)) Thanks [@shakkernerd](https://github.com/shakkernerd), [@TurboTheTurtle](https://github.com/TurboTheTurtle), [@NianJiuZst](https://github.com/NianJiuZst), [@zhouhe-xydt](https://github.com/zhouhe-xydt), [@luoyanglang](https://github.com/luoyanglang), and [@Solvely-Colin](https://github.com/Solvely-Colin). - Memory, state, and diagnostics recover cleaner: oversized OpenAI embedding batches split before 431s, QMD memory search stays available in transient mode, SQLite avoids WAL on NFS state volumes, stuck-session recovery scheduling no longer resets warning backoff, and Infinity chunk limits stay genuinely unbounded. ([#92650](openclaw/openclaw#92650), [#92618](openclaw/openclaw#92618), [#92639](openclaw/openclaw#92639), [#91247](openclaw/openclaw#91247), [#92752](openclaw/openclaw#92752), [#92735](openclaw/openclaw#92735)) Thanks [@mushuiyu886](https://github.com/mushuiyu886), [@TurboTheTurtle](https://github.com/TurboTheTurtle), [@849261680](https://github.com/849261680), [@gnanam1990](https://github.com/gnanam1990), and [@yhterrance](https://github.com/yhterrance). ##### Changes - Providers/models: add GLM-5.2 support and Claude Haiku 4.5 catalog entries while keeping provider-qualified model IDs normalized across OpenRouter and Google Vertex paths. ([#92796](openclaw/openclaw#92796), [#90116](openclaw/openclaw#90116), [#92627](openclaw/openclaw#92627), [#91218](openclaw/openclaw#91218)) Thanks [@arkyu2077](https://github.com/arkyu2077), [@liuhao1024](https://github.com/liuhao1024), and [@bymle](https://github.com/bymle). - Channel plugins: ship Telegram rich-message delivery and WhatsApp ACP binding support, including rich prompt handoff to CLI backends and transport fixtures for richer drafts. ([#92679](openclaw/openclaw#92679), [#92513](openclaw/openclaw#92513)) Thanks [@obviyus](https://github.com/obviyus) and [@TurboTheTurtle](https://github.com/TurboTheTurtle). - Agent commands: support `/btw` in CLI-backed sessions and keep CLI usage-error exits classified as usage failures instead of successful runs. ([#92669](openclaw/openclaw#92669), [#92162](openclaw/openclaw#92162)) Thanks [@joshavant](https://github.com/joshavant) and [@Pandah97](https://github.com/Pandah97). - Usage hooks: add built-in full footer rendering, default footer templates, per-turn usage state, credential-aware limits, and fixed-decimal formatting for usage-bar templates. ([#92657](openclaw/openclaw#92657), [#89835](openclaw/openclaw#89835), [#89629](openclaw/openclaw#89629)) Thanks [@Marvinthebored](https://github.com/Marvinthebored). - Docs and operator guidance: document node config examples, clarify before-install hook scope, correct agent default concurrency comments, refresh ZAI provider docs, and update channel/group docs for current Telegram and WhatsApp behavior. ([#92677](openclaw/openclaw#92677), [#92766](openclaw/openclaw#92766), [#92695](openclaw/openclaw#92695)) Thanks [@liuhao1024](https://github.com/liuhao1024), [@sallyom](https://github.com/sallyom), and [@ArielSmoliar](https://github.com/ArielSmoliar). ##### Fixes - Onboarding/skills: show the Homebrew install recommendation only on macOS and Linux, so FreeBSD and other unsupported platforms no longer get a misleading brew prompt. Fixes [#68893](openclaw/openclaw#68893); carries forward [#68894](openclaw/openclaw#68894), [#68910](openclaw/openclaw#68910), [#68941](openclaw/openclaw#68941), [#68943](openclaw/openclaw#68943), [#69002](openclaw/openclaw#69002), and [#69545](openclaw/openclaw#69545). Thanks [@yurivict](https://github.com/yurivict), [@Sanjays2402](https://github.com/Sanjays2402), [@Eruditi](https://github.com/Eruditi), [@JustInCache](https://github.com/JustInCache), [@nnish16](https://github.com/nnish16), and [@Mlightsnow](https://github.com/Mlightsnow). - Channels and delivery: preserve account-scoped DM channel send policy, rich Telegram final replies, rich Telegram tables and lists, Telegram thread-create CLI remapping, Slack outbound `message_sent` hooks, contributed message-tool schema optionality, same-channel generated media completions, and channel chunking around surrogate pairs and Infinity limits. ([#92788](openclaw/openclaw#92788), [#92679](openclaw/openclaw#92679), [#89421](openclaw/openclaw#89421), [#89943](openclaw/openclaw#89943), [#91137](openclaw/openclaw#91137), [#91246](openclaw/openclaw#91246), [#92735](openclaw/openclaw#92735)) Thanks [@yetval](https://github.com/yetval), [@obviyus](https://github.com/obviyus), [@spacegeologist](https://github.com/spacegeologist), [@rishitamrakar](https://github.com/rishitamrakar), [@lundog](https://github.com/lundog), [@TurboTheTurtle](https://github.com/TurboTheTurtle), and [@yhterrance](https://github.com/yhterrance). - Auto-reply/groups: keep ordinary group text replies on automatic final-reply delivery while allowing `message(action=send)` for files, images, and other attachments to the same group or topic. Carries forward [#43276](openclaw/openclaw#43276); refs [#48004](openclaw/openclaw#48004). Thanks [@NayukiChiba](https://github.com/NayukiChiba) and [@ShakaRover](https://github.com/ShakaRover). - Auto-reply/skills: preserve multiline payloads for `/skill` and direct skill slash commands while keeping command-head normalization for aliases, colon syntax, and bot mentions. Fixes [#79155](openclaw/openclaw#79155); carries forward [#81305](openclaw/openclaw#81305). Thanks [@web3blind](https://github.com/web3blind). - iMessage: normalize leading NUL sent-message echo prefixes while preserving interior NUL bytes and the leading attributedBody marker handling from [#73942](openclaw/openclaw#73942). Carries forward [#63581](openclaw/openclaw#63581). Thanks [@drvoss](https://github.com/drvoss). - Discord: give generated auto-thread titles a 60-second timeout and 4,096-token reasoning-model output budget, clamped to the selected model output cap. ([#64734](openclaw/openclaw#64734)) Thanks [@hanamizuki](https://github.com/hanamizuki). - Agent, cron, and Gateway runtime: mark active main sessions before restart shutdown aborts, pause yielded subagent runs whose terminal also signals abort, preserve yielded media completions, de-duplicate main-session heartbeat events, expose session identity in runtime prompts, reject unknown OpenAI agent selectors, keep generated media completions and slash-command block replies in WebChat, preserve fresh post-compaction usage while clearing stale usage snapshots, and require admin privileges for HTTP session/model override surfaces. ([#91357](openclaw/openclaw#91357), [#92631](openclaw/openclaw#92631), [#92146](openclaw/openclaw#92146), [#91287](openclaw/openclaw#91287), [#92468](openclaw/openclaw#92468), [#92510](openclaw/openclaw#92510), [#91246](openclaw/openclaw#91246), [#50795](openclaw/openclaw#50795), [#50845](openclaw/openclaw#50845), [#82874](openclaw/openclaw#82874), [#92651](openclaw/openclaw#92651), [#92646](openclaw/openclaw#92646)) Thanks [@ooiuuii](https://github.com/ooiuuii), [@openperf](https://github.com/openperf), [@IWhatsskill](https://github.com/IWhatsskill), [@ZengWen-DT](https://github.com/ZengWen-DT), [@zhangguiping-xydt](https://github.com/zhangguiping-xydt), [@Hollychou924](https://github.com/Hollychou924), [@leno23](https://github.com/leno23), and [@TurboTheTurtle](https://github.com/TurboTheTurtle). - Agents/exec: default empty-success background completion notices on only for real chat channels, preserving explicit opt-outs and keeping generic providers silent while carrying forward the narrow UX intent from [#39726](openclaw/openclaw#39726) and [#46926](openclaw/openclaw#46926). Thanks [@Sapientropic](https://github.com/Sapientropic) and [@wenkang-xie](https://github.com/wenkang-xie). - Providers and model replay: preserve storeless OpenAI Responses replay compatibility, avoid eager tool streaming for Claude 4.5 in Copilot, honor profile auth for SecretRef model entries, bound model browsing, strip provider prefixes where runtimes need bare IDs, and surface nested embedding fetch failures. ([#90706](openclaw/openclaw#90706), [#75393](openclaw/openclaw#75393), [#90686](openclaw/openclaw#90686), [#92247](openclaw/openclaw#92247), [#92627](openclaw/openclaw#92627), [#91218](openclaw/openclaw#91218), [#92628](openclaw/openclaw#92628)) Thanks [@snowzlm](https://github.com/snowzlm), [@Kailigithub](https://github.com/Kailigithub), [@rohitjavvadi](https://github.com/rohitjavvadi), [@samson910022](https://github.com/samson910022), [@liuhao1024](https://github.com/liuhao1024), [@bymle](https://github.com/bymle), and [@mushuiyu886](https://github.com/mushuiyu886). - Memory, state, diagnostics, and config: split header-too-large embedding batches, keep QMD memory search enabled in transient mode, avoid SQLite WAL on NFS volumes, preserve recovery scheduling outside stuck-session warning backoff, and keep shell environment fallbacks contained in config write tests. ([#92650](openclaw/openclaw#92650), [#92618](openclaw/openclaw#92618), [#92639](openclaw/openclaw#92639), [#91247](openclaw/openclaw#91247), [#92752](openclaw/openclaw#92752)) Thanks [@mushuiyu886](https://github.com/mushuiyu886), [@TurboTheTurtle](https://github.com/TurboTheTurtle), [@849261680](https://github.com/849261680), and [@gnanam1990](https://github.com/gnanam1990). - Workspace setup state: store setup completion outside the workspace dot directory using an OpenClaw-named root file, migrate valid legacy state forward, and avoid clobbering generic root `workspace-state.json` files for TigerFS-style dot-path compatibility. This Clownfish replacement carries forward the focused [#53326](openclaw/openclaw#53326) fix idea because the original branch was closed and uneditable. ([#53326](openclaw/openclaw#53326), [#44783](openclaw/openclaw#44783), [#39446](openclaw/openclaw#39446)) Thanks [@1qh](https://github.com/1qh). - UI/mobile/TUI: preserve dashboard session parent lineage, WebChat backscroll, reset soft command args, sidebar session picker interactivity, collapsed workspace files, resolved `/model` confirmation refs, and stale foreground iOS Gateway reconnects. ([#90658](openclaw/openclaw#90658), [#92622](openclaw/openclaw#92622), [#91353](openclaw/openclaw#91353), [#92705](openclaw/openclaw#92705), [#92779](openclaw/openclaw#92779), [#92773](openclaw/openclaw#92773), [#92552](openclaw/openclaw#92552)) Thanks [@luoyanglang](https://github.com/luoyanglang), [@TurboTheTurtle](https://github.com/TurboTheTurtle), [@zhouhe-xydt](https://github.com/zhouhe-xydt), [@NianJiuZst](https://github.com/NianJiuZst), [@shakkernerd](https://github.com/shakkernerd), [@NarahariRaghava](https://github.com/NarahariRaghava), and [@Solvely-Colin](https://github.com/Solvely-Colin). - TUI: reload the active session after external `/new` or `/reset` session-change events so stale transcript and stream state clear promptly. Fixes [#38966](openclaw/openclaw#38966); carries forward [#40472](openclaw/openclaw#40472). Thanks [@yizhanzjz](https://github.com/yizhanzjz) and [@wsyjh8](https://github.com/wsyjh8). - Control UI: preserve Gateway Access tokens during same-normalized WebSocket URL edits and reload gateway-scoped tokens when switching endpoints. Fixes [#41545](openclaw/openclaw#41545); repairs [#42001](openclaw/openclaw#42001) with additional source PRs [#41546](openclaw/openclaw#41546), [#41552](openclaw/openclaw#41552), and [#41718](openclaw/openclaw#41718). Thanks [@wsyjh8](https://github.com/wsyjh8), [@llagy0020](https://github.com/llagy0020), [@llagy007](https://github.com/llagy007), [@pingfanfan](https://github.com/pingfanfan), and [@zheliu2](https://github.com/zheliu2). - Gateway CLI: tolerate a single transient clean WebSocket close before `hello-ok` so one-shot RPC calls reconnect instead of failing noisily, while repeated clean pre-hello closes still surface. Carries forward source PRs [#54475](openclaw/openclaw#54475) and [#54774](openclaw/openclaw#54774); [#85253](openclaw/openclaw#85253) covered adjacent connect assembly diagnostics. Thanks [@ruanrrn](https://github.com/ruanrrn). - Gateway/Linux: keep root-owned systemd user service lifecycle commands on root's user manager when a stale `SUDO_USER` remains in a root shell with root's user bus environment. Fixes [#81410](openclaw/openclaw#81410). Thanks [@Ericksza](https://github.com/Ericksza) and [@ChuckClose-tech](https://github.com/ChuckClose-tech). - Release and test reliability: extend slow Gateway/full-suite watchdogs, split local full-suite shards when throttled, stabilize plugin auth marker fixtures, avoid brittle provider-ref error text, and keep QA Lab bootstrap selection assertions aligned with flow-only scenarios. ([#92652](openclaw/openclaw#92652)) - macOS Peekaboo bridge: update the embedded Peekaboo package to 3.5.2 and route bundled-skill CLI commands through the OpenClaw app bridge so they inherit its Screen Recording and Accessibility grants. - Agent routing: route subagent RPC callbacks addressed to an agent-shaped `--to` target to the correct session key instead of falling back to the main session, so WeChat (and other channel) session-key callbacks reach the intended subagent session. ([#90231](openclaw/openclaw#90231)) Thanks [@zhangguiping-xydt](https://github.com/zhangguiping-xydt). - Cron: preserve model, fallback, thinking, timeout, light-context, unsafe-content, and tool allow-list overrides on implicit text payloads by promoting them to agent turns, while explicit system events still prune those fields. Fixes [#28905](openclaw/openclaw#28905); carries forward [#64060](openclaw/openclaw#64060) and [#73946](openclaw/openclaw#73946). Thanks [@liaoandi](https://github.com/liaoandi). - QQBot delivery: keep markdown table chunks self-contained across message boundaries by preserving table state across block deliveries, flushing unfinished table-row fragments as plain text, and detecting short pipe-terminated rows by column count so split rows are not sent as malformed markdown. ([#92428](openclaw/openclaw#92428)) Thanks [@sliverp](https://github.com/sliverp). </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about these updates again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).  Reviewed-on: https://git.erwanleboucher.dev/eleboucher/homelab/pulls/1144

The built-in default footer (added in openclaw#92657) only defined a `discord` surface. Telegram and every other surface fall through to `output.default`, which was authored for a wide terminal: space-separated badges, a leading space-less join onto the message body, and ↕️ token + 🗄 cache% segments. On a narrow Telegram screen this wrapped at arbitrary spaces (often mid-meter or between 📚 and its bar) and welded onto the end of the message text. Make `default` read well on a phone: - Leading \n so the footer sits on its own line below the body. - Tight badges (no separators between model/flags/reasoning/fast). - NBSP before "|" and 💰; 📚 glued hard to the meter so it can't wrap there. - Single regular space after "|" as the only sanctioned wrap point. - Drop ↕️ tokens and 🗄 cache% from the default — noise for most users (still available to anyone via a custom messages.usageTemplate). Discord surface trimmed to match for consistency (keeps its -# dim header).

The built-in default footer (added in #92657) only defined a `discord` surface. Telegram and every other surface fall through to `output.default`, which was authored for a wide terminal: space-separated badges, a leading space-less join onto the message body, and ↕️ token + 🗄 cache% segments. On a narrow Telegram screen this wrapped at arbitrary spaces (often mid-meter or between 📚 and its bar) and welded onto the end of the message text. Make `default` read well on a phone: - Leading \n so the footer sits on its own line below the body. - Tight badges (no separators between model/flags/reasoning/fast). - NBSP before "|" and 💰; 📚 glued hard to the meter so it can't wrap there. - Single regular space after "|" as the only sanctioned wrap point. - Drop ↕️ tokens and 🗄 cache% from the default — noise for most users (still available to anyone via a custom messages.usageTemplate). Discord surface trimmed to match for consistency (keeps its -# dim header).

The built-in default footer (added in openclaw#92657) only defined a `discord` surface. Telegram and every other surface fall through to `output.default`, which was authored for a wide terminal: space-separated badges, a leading space-less join onto the message body, and ↕️ token + 🗄 cache% segments. On a narrow Telegram screen this wrapped at arbitrary spaces (often mid-meter or between 📚 and its bar) and welded onto the end of the message text. Make `default` read well on a phone: - Leading \n so the footer sits on its own line below the body. - Tight badges (no separators between model/flags/reasoning/fast). - NBSP before "|" and 💰; 📚 glued hard to the meter so it can't wrap there. - Single regular space after "|" as the only sanctioned wrap point. - Drop ↕️ tokens and 🗄 cache% from the default — noise for most users (still available to anyone via a custom messages.usageTemplate). Discord surface trimmed to match for consistency (keeps its -# dim header).

openclaw-barnacle Bot added size: S triage: needs-real-behavior-proof Candidate: external PR needs after-fix proof from a real setup. labels Jun 13, 2026

clawsweeper Bot had a problem deploying to qa-live-shared June 13, 2026 11:31 Failure

openclaw-barnacle Bot added the docs Improvements or additions to documentation label Jun 13, 2026

Marvinthebored changed the title ~~feat(usage): built-in "default" /usage full footer template (hidden opt-in)~~ feat(usage): authorable /usage full footer — built-in default, merge-over-default, docs Jun 13, 2026

obviyus self-assigned this Jun 13, 2026

obviyus changed the title ~~feat(usage): authorable /usage full footer — built-in default, merge-over-default, docs~~ feat(usage): ship built-in /usage full footer Jun 13, 2026

openclaw-barnacle Bot added size: M and removed size: S proof: sufficient ClawSweeper judged the real behavior proof convincing. labels Jun 13, 2026

Peetiegonzalez and others added 5 commits June 13, 2026 19:00

fix(usage): simplify default full footer

ee77255

test(usage): align full footer contract

738d729

fix(usage): reject empty footer templates

9f0bb17

obviyus added 2 commits June 13, 2026 19:00

fix(usage): preserve partial footer counts

194bb6a

fix(usage): warn on broken footer templates

eabebf3

obviyus force-pushed the usage-footer-default-template branch from fff560b to eabebf3 Compare June 13, 2026 13:31

fix(usage): suppress unknown total-only cost

071c823

clawsweeper Bot added the proof: sufficient ClawSweeper judged the real behavior proof convincing. label Jun 13, 2026

obviyus merged commit 7994880 into openclaw:main Jun 13, 2026
173 of 175 checks passed

This was referenced Jun 14, 2026

feat: include model in response usage footer #56081

Closed

Feature request: per-message token/cost metadata in mobile app and channel surfaces #72133

Open

This was referenced Jun 16, 2026

[Feature]: Expose AI model used and usage cost when using openrouter/auto #7006

Closed

Feature Request: Add usageDefault config option for per-session token display #12578

Closed

This was referenced Jun 16, 2026

Bug: Configuration Migration Failure During Upgrade (v3.24 → v3.28) #57567

Closed

feat: server-rendered status footer and context threshold warnings #72005

Closed

clawsweeper Bot mentioned this pull request Jun 25, 2026

claude-cli backend: no pre-compaction handoff flush + scary bare 100% context display #96858

Closed

Marvinthebored mentioned this pull request Jun 30, 2026

pipeline: normalized provider→channel stream grammar (core) #93342

Closed

clawsweeper Bot mentioned this pull request Jul 1, 2026

fix(usage): make built-in footer easier to wrap on Telegram #92877

Merged

clawsweeper Bot mentioned this pull request Jul 2, 2026

fix(usage-bar): evict oldest template cache entry when full #98853

Closed

programmingWTF mentioned this pull request Jul 2, 2026

docs(changelog): add missing PR #92654 (right-click Reply in Dashboard webchat) #99009

Closed

clawsweeper Bot mentioned this pull request Jul 7, 2026

[Feature]: Per-agent cost budget enforcement at the gateway level #42475

Open

This was referenced Jul 13, 2026

Feature Request: Add premium request % to /usage footer #7379

Open

fix: restore Braille meter rendering without broad character filter #106187

Open

fix(usage-bar): add webchat surface with block scale to prevent Braille character leak #106235

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

feat(usage): ship built-in /usage full footer#92657

feat(usage): ship built-in /usage full footer#92657
obviyus merged 9 commits into
openclaw:mainfrom
Marvinthebored:usage-footer-default-template

Marvinthebored commented Jun 13, 2026 •

edited by obviyus

Loading

Uh oh!

clawsweeper Bot commented Jun 13, 2026 •

edited

Loading

Uh oh!

Uh oh!

obviyus commented Jun 13, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Uh oh!

Conversation

Marvinthebored commented Jun 13, 2026 • edited by obviyus Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Real behavior proof

Verification

Uh oh!

clawsweeper Bot commented Jun 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

obviyus commented Jun 13, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Marvinthebored commented Jun 13, 2026 •

edited by obviyus

Loading

clawsweeper Bot commented Jun 13, 2026 •

edited

Loading