Usage 0.29.22: Custom Codex data folders no longer look empty

Release notes

FEATURE

Custom Codex data folders no longer look empty

If you keep Codex data somewhere other than its default folder, usage could previously treat it as nonexistent: the Codex section appeared empty, with no explanation. The culprit was the CODEX_HOME environment variable, a hidden setting supplied before a program starts. It can point to a Codex data folder for multiple accounts or containerized setups, but seven places in usage that read the data were still hardcoded to ~/.codex/. It was like moving house, updating your address, and having seven delivery drivers continue to visit the old one. They now all ask the same codex_paths.codex_home() helper for directions: use CODEX_HOME when set, otherwise fall back to ~/.codex/. Your custom-folder data can show up again.

Original changelog

Original changelogCustom Codex data folders no longer look empty

**Codex data was unreadable for anyone with a custom `CODEX_HOME`.** Every path into Codex's local data (`codex_loader.py`, `adapters/codex.py`, `session_hooks.py`, `setup_hook.py`, `fsevents_watch.py`, `menubar_state.py`, `analyzer/subscription.py`) was hardcoded to `~/.codex/...`, so anyone who set the `CODEX_HOME` environment variable — multiple accounts, containerized setups — got an empty Codex section with no explanation. All of them now resolve through a single `codex_paths.codex_home()` helper that honors `CODEX_HOME` and falls back to `~/.codex/` when it's unset.