Codex Profile Longest task does not update for completed /goal runs

Codex
1

I filed a Codex profile stats bug where the Profile “Longest task” value does not update for completed long-running /goal tasks:

The short version:

  • My Profile stat remains stuck at 3h 48m.
  • I ran a completed 8h+ /goal after the Profile / “Longest task” feature was already visible.
  • Local CLI history also shows a PRISM /goal session spanning about 53.63h.
  • The local goals_1.sqlite thread_goals table exists, but count(*) is 0.

I found the related goal-storage threads too, especially openai/codex#23984 and openai/codex#25407. The fixes/workarounds people reported there were:

  • fully restart Codex and any stale codex app-server processes so app-server and CLI versions match;
  • make sure the goals feature flag is not explicitly disabled;
  • if thread/goal/get failures persist, back up and rebuild the local Codex state DB files as OpenAI staff suggested.

That helps explain broken /goal reads/writes, but this case seems like a separate downstream persistence/backfill issue: the raw long-running session history exists, but the completed goal did not make it into the Profile “Longest task” stat.

Has anyone else seen Profile stats stay stuck after a successful long-running /goal, especially after restarting/updating Codex?

1 Like