Feature request: optional `isHidden` field to hide a custom metrics card

[inouekoshi]

Motivation

I use custom metrics to show CLI sessions (Claude Code / Antigravity CLI) via their statusline hooks. When the CLI is not running, the card keeps showing stale values.

Deleting the JSON file is not an option, because the card then shows "Last updated: Failed" in red (per the documented failure behavior). My current workaround is a launchd job that detects the process being gone and rewrites the file with metrics: [], which collapses the card to its title — close, but the card is still there.

Proposal

An optional top-level boolean, e.g. "isHidden": true:

{
  "title": "Claude Code",
  "symbol": "staroflife",
  "isHidden": true,
  "metrics": [],
  "lastUpdatedDate": "2026-07-16T02:30:00Z"
}

When true:

• the card is hidden from the dashboard (the source stays registered in Settings)
• the Metrics Bar entry is hidden as well

Omitted or false keeps the current behavior, so existing JSON files are unaffected. This also fits the "producer owns the presentation" design — the producer already decides what to show, and this would let it decide whether to show.

Use cases

• CLI/session-bound cards that are only meaningful while the process is running (Claude Code, Codex, Antigravity CLI, ...)
• Alert-style cards that should appear only when something needs attention (backup overdue, battery low, quota nearly exhausted)

Thanks for RunCat Neo and the custom metrics feature — the JSON-file design is a joy to build on!

[Kyome22]

@inouekoshi Thank you for your sharp and insightful suggestion.
I completely understand what you are getting at, but I believe adopting this idea won't be that straightforward.

RunCat Neo already has its own show/hide settings for the dashboard and metrics bar. Adding another layer of show/hide settings via JSON would make the conditions overly complex. For instance, I am concerned it would lead to an increase in support inquiries from users wondering why things aren't displaying as expected. Furthermore, having the UI's occupied space change dynamically because elements appear and disappear depending on the timing might not be very user-friendly. In fact, I purposely applied a monospaced font to the numeric displays just to prevent the displayed width from changing.