openclaw - 💡(How to fix) Fix Feature: per-agent status card field suppression (hide usage/billing from specific agents)

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Root Cause

Agent A serves User A (account owner). Agent B serves User B (partner/friend). User B should not see subscription usage percentages because it creates unnecessary anxiety about "using too much" — even when usage is perfectly fine. The behavioral workaround (instructing Agent B to never discuss costs) is fragile; a structural solution is better.

Fix Action

Fix / Workaround

Agent A serves User A (account owner). Agent B serves User B (partner/friend). User B should not see subscription usage percentages because it creates unnecessary anxiety about "using too much" — even when usage is perfectly fine. The behavioral workaround (instructing Agent B to never discuss costs) is fragile; a structural solution is better.

Current Workaround

Code Example

{
  "agents": {
    "list": [
      {
        "id": "my_agent",
        "status": {
          "hideUsage": true
        }
      }
    ]
  }
}
RAW_BUFFERClick to expand / collapse

Problem

The /status command (session_status tool) exposes provider usage percentages (e.g. "Premium 7% left") to all agents equally. In multi-agent setups where different agents serve different users, this creates an information leak — a secondary agent's user can see the account owner's subscription usage, which may cause unintended concern about costs.

Proposed Solution

Add a per-agent configuration option to suppress specific status card sections:

{
  "agents": {
    "list": [
      {
        "id": "my_agent",
        "status": {
          "hideUsage": true
        }
      }
    ]
  }
}

When hideUsage: true is set for an agent, the 📊 Usage: line should be omitted from that agent's status card output entirely.

Possible Extensions

  • hideSections: ["usage", "cache", "context"] for more granular control
  • status.visible: ["model", "session", "queue"] allowlist approach

Use Case

Agent A serves User A (account owner). Agent B serves User B (partner/friend). User B should not see subscription usage percentages because it creates unnecessary anxiety about "using too much" — even when usage is perfectly fine. The behavioral workaround (instructing Agent B to never discuss costs) is fragile; a structural solution is better.

Current Workaround

Add prompt-level rules to the agent's AGENTS.md forbidding cost/usage discussion. Works ~95% of the time but breaks if the user directly invokes /status.

extent analysis

TL;DR

Implement a per-agent configuration option to suppress specific status card sections, such as setting hideUsage: true for agents that should not display subscription usage percentages.

Guidance

  • Review the proposed solution and consider adding a hideUsage option to the agent configuration to omit the usage line from the status card output.
  • Evaluate the possible extensions, such as hideSections or status.visible, to determine if more granular control is needed.
  • Test the configuration change with different agent setups to ensure the desired behavior.
  • Consider the use case where Agent B serves User B and should not display subscription usage percentages to prevent unnecessary anxiety.

Example

{
  "agents": {
    "list": [
      {
        "id": "agent_b",
        "status": {
          "hideUsage": true
        }
      }
    ]
  }
}

Notes

The current workaround using prompt-level rules in AGENTS.md is not foolproof, as it can be bypassed by directly invoking the /status command. A structural solution, such as the proposed configuration option, is likely a more reliable approach.

Recommendation

Apply the proposed workaround by adding a hideUsage option to the agent configuration, as it directly addresses the information leak issue and provides a more robust solution than the current behavioral workaround.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix Feature: per-agent status card field suppression (hide usage/billing from specific agents)