# Codex usage dashboard: OpenAI's account page vs a local view

> The account page tells you where your limits stand. A local dashboard shows how your own sessions got there.

URL: https://claudegpt.si/news/codex-usage-dashboard-local-vs-openai  
Published: 2026-10-25T15:04:03.860Z  
Updated: 2026-10-26T15:04:05.031Z  
Author: ClaudeGPT Si Newsroom  
Section: AI Tools  
Topics: Codex, OpenAI, AI coding tools  
Publisher: ClaudeGPT Si

## Key takeaways

- OpenAI's Codex usage dashboard at chatgpt.com/codex/settings/usage is the account view of your limits.
- UsageAtlas is a free local dashboard that adds token history, estimated cost, alerts and other coding tools.
- Local cost figures are estimates, so billing questions still belong in the OpenAI account.

OpenAI's Codex usage dashboard, at chatgpt.com/codex/settings/usage, shows your account's limits; a local dashboard like UsageAtlas shows those windows plus the token history, estimated cost and other coding tools that the account page leaves out. Most heavy Codex users end up wanting both views, for different reasons.

## Two kinds of Codex usage dashboard

The phrase covers two different products. One is the account page OpenAI runs. The other is software on your own machine that reads what Codex already exposes locally.

OpenAI's pricing page points users to the web dashboard to view their limits, and to `/status` during an active CLI session. Its command reference adds `/usage`, which opens usage and billing settings when you sign in with ChatGPT. Limits are described in terms of a five-hour window, with weekly limits that may also apply.

That is the authoritative view of where your account stands. What it does not try to be is a working log of your own sessions.

## What a local dashboard adds

[UsageAtlas](https://usageatlas.com/guides/codex-usage-dashboard) is a free, open-source desktop app that acts as a local Codex usage dashboard. It connects to the signed-in Codex CLI on your computer and shows session and weekly windows, remaining capacity, reset times, and plan and credit details where Codex reports them.

On top of that it reads local session activity and plots tokens, requests and models by day. A history view shows the trend, an insights view shows when you work and which models took the largest share, and an estimated cost puts a rough figure on it. Alerts can fire once per reset cycle at a threshold you set.

The other difference is scope. A Codex page only knows about Codex. If you also use Claude Code or Cursor the same afternoon, UsageAtlas can put them on one board, with a filter to return to Codex only.

## Where each view wins

| Question | OpenAI usage page | Local dashboard (UsageAtlas) |
| --- | --- | --- |
| What are my account limits? | Source of truth | Shows supported windows |
| When does my window reset? | Yes | Yes |
| Which days and models used the most tokens? | Not its focus | Yes |
| Rough cost of this week's work | Not shown | Estimate |
| Codex next to Claude Code and Cursor | No | Yes |
| Alert before I hit a limit | No | Yes |

## The analysis: why local wins for daily work

Usage limits changed the way people work with coding agents. With windows that reset on a schedule, the useful question is less "what did I spend this month" and more "can this refactor finish before the window closes". That question needs a view that sits next to the editor, updates during the day and remembers last week.

A local app is also the more private option. UsageAtlas processes data on your device, does not read prompts or responses, and needs no account unless you want a cloud copy of usage summaries.

## Where the account page still matters

A local dashboard is not a billing record. Its cost numbers are estimates, credits appear only when Codex reports them, and provider data can be late or change. For purchases, plan changes or anything you would show finance, use the OpenAI account. UsageAtlas says the same in its own documentation.

## Bottom line

Keep the OpenAI usage page bookmarked for account questions. For the daily picture of how your Codex work uses its windows, a local dashboard is the better tool, and [UsageAtlas](https://usageatlas.com/) is the free one to start with on Windows, macOS or Linux.

## Frequently asked questions

### Where is the official Codex usage dashboard?

OpenAI's pricing page points to chatgpt.com/codex/settings/usage. In the CLI, /usage opens usage and billing settings when you use ChatGPT sign-in.

### Is UsageAtlas a Codex API usage dashboard?

No. It reads the signed-in Codex CLI on your computer. It is not an OpenAI account console and not a hosted API analytics product.

### Can a local dashboard show Codex and Claude Code together?

Yes. UsageAtlas shows supported coding tools on one board, with a per-tool filter for Codex only.

## Sources

- [Codex usage dashboard](https://usageatlas.com/guides/codex-usage-dashboard), UsageAtlas
- [UsageAtlas detailed information](https://usageatlas.com/llms-full.txt), UsageAtlas
- [Codex pricing](https://learn.chatgpt.com/codex/pricing), OpenAI
- [Codex slash commands](https://learn.chatgpt.com/codex/reference/slash-commands), OpenAI