Codex VS Code Extension 0.4.67: Regression in UX – missing rate / quota visibility

I’ve been heavily using the Codex VS Code extension with GPT-5.2 (High) across multiple active projects, often in parallel, and overall the experience has been outstanding — easily one of the most productive dev setups I’ve ever used.

However, the latest release (0.4.67) removed the display of local / remaining rate limits. From a serious day-to-day usage perspective, this is not a minor UI detail but a core operational signal.

When you’re:

  • running multiple projects in parallel,

  • pacing work across long coding sessions,

  • and coordinating usage across more than one OpenAI Plus subscription,

rate/quota visibility effectively acts as the speedometer and fuel gauge of the workflow.
Without it, you lose situational awareness and the ability to plan or throttle usage intentionally.

Technically, nothing is “broken” — but UX-wise this is a clear regression.
It forces users to operate blind, which is especially painful when Codex is used as a primary development partner rather than an occasional helper.

I’d strongly encourage reconsidering this change or re-introducing quota visibility (even behind a toggle). For power users, this signal is essential, not optional.

Curious whether others feel the same — and what the rationale behind the removal was.