# Agents widget attributes Pi/OpenAI usage to Codex and shows Codex error after Codex uninstall

## Summary

The Omarchy top-bar Agents widget appears to treat Pi sessions that use the `openai-codex`/OpenAI provider as `Codex` usage. After uninstalling the Codex CLI and setting Pi as the default agent, the top bar still showed Codex, with a red/unhealthy state saying Codex was not configured/available.

This is confusing because the active/default agent is Pi, not Codex.

## Environment

- Omarchy version: `4.0.1-1`
- Default agent: `pi`
- `pi` is installed and on PATH
- `codex` was uninstalled and is no longer on PATH

Relevant local checks:

```text
$ omarchy-default-agent
pi

$ command -v pi
/home/samk13/.local/share/mise/installs/pi/latest/pi/pi

$ command -v codex
# no output
```

## What happened

1. Pi was configured as the default agent.
2. Codex CLI was uninstalled.
3. The top-bar Agents widget still showed `Codex`.
4. The Codex entry was marked red/unhealthy and indicated it was not configured/available.
5. The stale usage record looked like this:

```json
{
  "id": "codex",
  "name": "Codex",
  "ready": true,
  "hasLocalStats": true,
  "totalPrompts": 111,
  "totalSessions": 7,
  "usageStatusText": "Codex unavailable",
  "authHelpText": "codex not found in PATH"
}
```

Pi session files on this machine contain messages with:

```json
"provider": "openai-codex"
```

So it looks like the Codex usage collector is picking up Pi/OpenAI usage and presenting it as the Codex agent/provider.

## Expected behavior

One of these would be less confusing:

- Pi usage should show as `Pi` in the Agents widget, even when the underlying API/provider is OpenAI/Codex-compatible; or
- If Codex CLI is not installed, the widget should not show a Codex subscription/provider purely because Pi sessions used an OpenAI/Codex-compatible backend; or
- The widget should distinguish “Pi using OpenAI/Codex-compatible API” from “Codex CLI/subscription”.

## Actual behavior

The Agents widget showed Codex after Codex was uninstalled, with a red/unavailable state (`codex not found in PATH`), even though Pi was the selected/default agent.

## Diagnostics

A diagnostic log was generated locally at:

```text
/tmp/omarchy-debug.log
```

Attach/upload that log if requested by maintainers.