[FEATURE]:[Severe UX Regression V2] Missing per‑model usage breakdown, forced new client layout, precipitous drop in paid‑subscription experience #52937

Feature hasn't been suggested before.

• I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

Description

After upgrading to openCode.ai V2, Go‑subscription paying users are seeing a very noticeable degradation in experience.

The web console has completely removed detailed usage logs. Now only weekly and monthly total consumption hours are shown for the 5‑hour quota. There is no way whatsoever to view the specific model for each individual call. This was a core capability in V1, which paying users relied on to audit and track quota consumption.

Question: Are there any hidden pages or APIs available to query usage breakdown split by model? I cannot find any relevant entry point at the moment.

The latest OpenCode client has outright removed the toggle for the legacy layout, forcing users onto the new interface. The new version has highly counter‑intuitive interaction logic, drastically reducing workflow efficiency, and gives users no option to keep using the old UI.

This release is an unmitigated disaster. The product manager should be fired. They cannot even copy the GPT console properly. If you cannot implement new features competently, do not touch stable, well‑working legacy versions. Practically all practical features relied on by long‑term users have been cut. Paying customers end up with a worse experience after the update.

Expected Behavior

• Restore the per‑model usage breakdown report. If a frontend page cannot be built for now, please advise whether an API exists to retrieve this dataset.
• Reinstate the layout‑switch toggle in the client, allowing users to revert to the old layout. Do not force‑enforce the new UI for everyone.
• Avoid bluntly removing high‑frequency core features during major‑version iterations. Do not push updates purely for the sake of redesigning things.

Additional Context

As a paying Go‑subscription user, quota auditing is a hard requirement. Without visibility into consumption per model, I have no idea how the 5‑hour quota is being used. This severely disrupts day‑to‑day usage. The full V1 workflow worked well. V2 qualifies as a typical destructive update.