You can check your Codex or Claude Code allowance from a phone browser using the provider's usage page. If you want that information on your Home Screen, Lock Screen or wrist, the setup needs a little more care: the display has to follow the right account and usage window, and you need to know when the reading was last updated.
Start with the provider's usage page
For Codex, open the official usage dashboard in your browser. Confirm that you are signed in to the account you use for Codex. OpenAI also documents /status for checking remaining limits during an active CLI session. API-key sessions have separate billing from your ChatGPT subscription allowance. These details are covered in OpenAI's pricing and usage documentation.
For Claude Code, open Claude Settings → Usage. Claude's account limits apply across its supported product surfaces, including Claude Code. Read each displayed window and its reset time; the windows available to you depend on your account and plan. Claude explains the distinction between account usage and conversation length in its usage-limit documentation.
Keep the official page available during setup. It gives you a reference when you choose which account and window to display elsewhere.
Connect the account on iPhone
For regular checks, TokenVive puts supported Codex and Claude Code allowances on iPhone and Apple Watch, with configurable Home Screen and Lock Screen widgets.
In TokenVive, open Settings, choose the service and follow its connection prompts. Complete the provider's sign-in or authorization flow on iPhone, then return to the app to finish connecting.
Open the account's usage view and check the available windows. If you have both personal and work accounts, confirm which one you are looking at before selecting a window. Read its remaining percentage, reset time and last successful update together.
TokenVive requires iOS 17 or later. AI connections and data refreshes require active TokenVive membership or remaining trial access. Your provider subscription remains separate.
Reading the selected account and usage window in TokenVive. Example values.
Choose a source for each widget
A TokenVive usage source identifies an account and one of its available usage windows. If an account exposes both session and weekly allowance, those are separate choices.
To add a Home Screen widget:
- Touch and hold an empty area of the Home Screen. Open Edit → Add Widget, or use the + button on older iOS versions.
- Find TokenVive, choose an available usage widget and size, then add it.
- Touch and hold the added widget and choose Edit Widget.
- Select the account and usage window you want to follow.
The multiple-account Home Screen widget supports up to three sources. You can use those positions for different accounts or for different available windows from the same account.
For the Lock Screen, touch and hold it, choose Customize, then open the widget area. Add a TokenVive usage widget and select its source while editing. Home Screen and Lock Screen widgets keep their own configurations, so check both when you change an account.
Apple's widget setup instructions cover the system menus. The TokenVive widget guide includes source selection and troubleshooting.
Phone widget and Watch app views. Configure the account and window for each view.
Set up the paired Apple Watch
Open TokenVive on both iPhone and its paired Apple Watch. The phone syncs the credentials needed for supported account queries; the Watch can then query those services directly. Sign-in and expired-session reconnection stay on iPhone.
The Watch app requires watchOS 10 or later. Its app view and watch face complications are separate surfaces, with different amounts of space for account details. Use the Watch app when you need to inspect more of a reading.
When comparing phone and Watch values, match the account and window first. Then compare their update times. Background transfers can arrive after a foreground refresh on the phone.
Check the labels before comparing percentages
A difference between two screens can be legitimate. For example, 30% used and 70% remaining can describe the same allowance. A session window and a weekly window can also show different percentages without either being wrong.
TokenVive's usage rings show remaining allowance. If a reading differs from the provider's page, check:
- Account and workspace: compare the same connection, especially when switching between work and personal access.
- Window or model group: compare the same allowance on both screens.
- Update time: refresh the account in TokenVive and check whether a newer result was obtained.
If a refresh fails, TokenVive keeps the last successful result and its original timestamp. An unavailable percentage or reset time stays unavailable. It should not be interpreted as zero usage.
Widgets can also lag behind the app. iOS controls their refresh opportunities, so the widget is a periodically updated view. A countdown reaching zero does not establish that a new provider reading has arrived.
Keep allowance and recorded use separate
Remaining allowance tells you what is available in a particular window. Token and message records describe past activity. A percentage alone cannot reconstruct those records or tell you exactly how many more prompts will fit.
In TokenVive, Codex analysis includes daily token totals across all models and message counts with available model breakdowns. Claude Code currently supports allowance checks without message or token analytics. History coverage and update timing depend on the data available for the account.
For an occasional check, the provider's usage page is a straightforward option. TokenVive adds configurable phone widgets and paired Watch access for supported accounts. The AI usage guide lists current service coverage and device requirements.
Official documentation checked November 21, 2026. Account rules and system menus can change.
Disclosure: the author develops TokenVive. The app is independent of OpenAI and Anthropic.


