Excessive Codex Usage Consumption During Deleted Chat Recovery Attempt

What version of the Codex App are you using (From “About Codex” dialog)?

Codex Desktop Version: 26.601.21317

What subscription do you have?

Workspace

What platform is your computer?

Microsoft Windows NT 10.0.26220.0 x64

What issue are you seeing?

Title: Excessive Codex Usage Consumption During Deleted Chat Recovery Attempt

Environment:

• Codex Desktop Version: 26.601.21317
• Model: GPT-5.5
• Workspace Plan

Issue:
I asked Codex to help locate deleted chats/conversations. During this request, Codex consumed an extremely large amount of usage quota, including approximately 25% of my weekly allocation from a single task.

Expected Behavior:
The task should either:

• report that deleted chats cannot be recovered, or
• perform a bounded search and return results.

Actual Behavior:
Codex entered a lengthy investigative workflow involving repeated searches of local session stores, caches, rollout files, SQLite databases, and related artifacts. The task generated millions of tokens and consumed a disproportionate amount of quota.

Evidence:

• Rollout/session log approximately 851 KB in size.
• Usage metrics in the log show multi-million-token consumption.
• Session files referenced in the log include .codex/sessions rollout files.
• The issue occurred while attempting to locate deleted chats after a cache-clearing operation.

Please investigate whether this represents:

• runaway agent behavior,
• excessive internal tool recursion,
• incorrect usage accounting,
• or a regression in Codex Desktop 26.601.

What steps can reproduce the bug?

Feedback ID: 019e9036-e443-71c1-8d65-46f44696ef2d

What is the expected behavior?

_No response_

Additional information

rollout-2026-06-04T05-36-15-019e91fd-8119-7380-aaa4-3af1ac0f4b35.zip