llmtrim status still not working w/Codex

[joe-crick]

What happened

When you run llmtrim status, only Claude code is reported--there is no data for Codex, despite Codex being the only AI agent running.

How are you running llmtrim?

• Proxy (llmtrim setup / serve) — intercepting a tool's traffic

• CLI (llmtrim compress / send / batch)

• Tool / client (proxy path):

• Provider:

• Preset / config:

Reproduce

Simple: Run llmtrim serve. Run llmtrim status.

Expected vs actual

• Expected:
  llmtrim status will show stats for Codex

• Actual:
  No stats show. I'm unable to determine if it's working with Codex at all.

Environment

• llmtrim --version: 0.11.3
• llmtrim status (daemon + CA + savings state):
• Install method: npm
• OS / arch: Debian 12

[fkiene]

Found it, and thanks for the screenshot: it held the key clue. The banner says "last request 412h22m ago" with a flat $0 trend. Your ledger recorded nothing from any tool for about 17 days while Codex ran through the proxy daily. So this wasn't a display bug; the proxy stopped understanding Codex requests around the end of June.

Root cause: Codex CLI 0.144+ compresses its request bodies with Content-Encoding: zstd. llmtrim intercepts the traffic fine (that's why killing it still kills Codex), but it couldn't parse the compressed bytes as JSON, so it forwarded each request untouched and recorded nothing. Your Codex kept working; the ledger stayed frozen; status kept showing your old Claude Code history.

I reproduced this with Codex 0.144.1 against a clean proxy: a completed turn left zero ledger rows. The request body started with the zstd magic bytes (28 b5 2f fd).

Fix is up in #194. The interceptor now decodes zstd and gzip request bodies before compression and tracking, and I also refreshed the Codex fingerprint (its system prompt changed in 0.144, which would have shown your sessions as "Unknown" instead of "Codex"). After the fix, the same turn records agent=codex with real token counts and shows up as a Codex card in status.

It ships in the next release. No workaround exists on 0.11.3, since the decoder is new code. One note for after you upgrade: your existing Claude Code history stays in the ledger, so the dashboard will show both. New Codex traffic will appear alongside it.