Agents panel never appears for active pi users on non-Anthropic/non-Codex backends (e.g. OpenRouter) #8270

System details

• Omarchy: 4.0.1-1
• Kernel: 7.1.9-arch1-2 (Arch x86_64)
• Compositor/shell: Hyprland + omarchy-shell (Quickshell)
• Default agent: pi (~/.config/omarchy/defaults/agent contains pi)

Summary

The omarchy.agents bar widget and panel never appear on a machine where pi — one of the agents Omarchy offers as a default in setup — is actively used, if pi is configured with a backend other than Anthropic or openai-codex (e.g., OpenRouter). Two days of heavy daily use produce no icon, no panel, and no hint anything is wrong.

What happens vs. what's expected

• Expected: Since both shipped collectors deliberately scan ~/.pi/agent/sessions/, using pi should eventually surface usage in the agents panel.
• Actual: All usage records stay at zero for any pi session not routed through the two recognized backends, so the widget self-hides permanently.

Steps to reproduce

1. Install Omarchy 4.0.1-1; set default agent to pi (omarchy-default-agent pi).
2. Configure pi with a non-Anthropic, non-Codex backend (in my case OpenRouter via the openai-completions API) and use it daily for 2+ days (334 assistant messages across multiple sessions).
3. Observe: no agents icon in the bar, no panel. Every record in ~/.local/state/omarchy/agents/usage/ reports zero prompts/sessions/active days.

Root cause analysis

The collectors scan pi's session directory on purpose but filter strictly by backend:

• omarchy-agent-usage-claude, scan_pi_usage():

  provider = str(message.get("provider") or "")
  if provider != "anthropic":
      continue

• omarchy-agent-usage-codex, scan_pi_sessions(): only counts entries where provider is openai-codex or api starts with openai-codex.

Meanwhile pi writes provider, model, and token usage on every assistant message regardless of which backend served it — so the data needed to count usage from any provider is already present in the JSONL.

Because every record ends up empty, Main.qml's enabledProviders list is empty and the widget collapses out of the bar by design ("with none, the module leaves the bar entirely"). That self-hiding behavior is reasonable when collectors are complete, but here it means an active agent user gets silence instead of a panel — and no diagnostic path to figure out why.

Suggested fix

Either:

1. A generic pi collector that records usage from pi session transcripts regardless of provider (one "pi" record aggregating all backends), or
2. Per-provider records derived from the same transcripts, matching how claude/codex tabs work today.

Option 1 seems simplest since the parsing logic (usage extraction by assistant message) already exists in scan_pi_usage() — it just needs the provider filter removed or widened.