OpenAI Codex on a second screen

Xenon’s Codex tile shows the usage windows of your plan, your tokens per day, the sessions working on your PC and every request they make, with Allow, Deny and Answer in Codex. It lives on the screen next to your PC: a Xeneon Edge, a monitor, a tablet or a paired phone.

Last updated: 6 October 2026

Add the tile from the + button, under System. The plan works as soon as Codex is installed and signed in on the PC. Sessions and approvals need Codex to be connected, which you do from the tile itself. It runs on Windows, and on macOS and Linux, which are in beta.

Plan usage

Codex reports the usage windows of your plan: how much of each is used and when it resets. Xenon shows each one as a bar with a countdown to its reset and a mark where an even pace would be now. The figures turn amber at 70% and red at 90%.

The length of each window comes from Codex, so the tile labels it as it is: on a paid plan that is usually 5 hours and a week, on the Free plan one window of 30 days.

The Usage side of the tile shows your tokens today, over 7 and 30 days and in total, with a column for each of the last 30 days. These are the numbers Codex reports for your whole account, every device and app included, not only this PC.

Sessions and recent conversations

With Codex connected, each session gets a row as it starts: what you asked it to do, the model, and whether it is working or waiting for you. Under them the tile lists the conversations Codex keeps, with where they ran: the ChatGPT app, the editor or the terminal.

Sessions come from Codex’s hooks. Codex runs them in the codex command; whether the ChatGPT app and the editor extension run them too depends on your version of Codex. The plan and the conversation list do not depend on hooks and cover all three.

Answering requests

When a Codex session asks to run a command or change files, the request appears on the tile with the command, or the files the change touches with deletes marked, and three buttons: Allow, Deny and Answer in Codex, which puts the question back in Codex at once. The card says what makes the request unusual: the network, publishing your work, a file outside the project, more access than the session has, or something that cannot be undone.

A request that cannot be undone, such as rm -rf or a patch that deletes a file, is allowed by holding the button, not by a tap. A request left for 25 seconds takes over the whole screen, so it does not sit unseen on another page.

Nothing is approved for you. While a request waits on the tile, Codex does not show its own prompt, so after 90 seconds, or if Xenon is closed, the request goes back to Codex, which asks as usual. Settings → Codex changes the wait or turns the requests off.

To answer from your phone, pair it with Xenon (beta). The phone shows the same dashboard, with the same buttons. How to pair a phone.

Connecting Codex

1. Add the Codex tile from the + button, under System.
2. On the tile, tap Codex, then Connect.
3. Open Codex, type /hooks and trust the Xenon hooks. Codex runs a new hook only after you trust it; Xenon never does this for you, because it is Codex’s own safety check.
4. Start a new session. Hooks reach the sessions started after this step, and the tile says whether Codex has the hooks trusted.

Connecting edits one file: your Codex hooks.json, in ~/.codex or the folder CODEX_HOME points to. It adds five hooks that run a small script of Xenon’s with Node, which reports to Xenon on 127.0.0.1, your own PC. Your own hooks stay as they are and in the same order, and Xenon does not touch config.toml.

Before the first change, Xenon saves a copy of the file next to it as hooks.json.xenon-backup. If the file cannot be read, Xenon leaves it as it is and says so.

Uninstalling Xenon takes out the hooks it added and deletes the backup; your own hooks are left alone. To do the same without uninstalling, tap Disconnect on the tile, or run node server/codex-link.js unlink in the folder Xenon is installed in.

What is sent where

The tile uses no API key and never reads your sign-in. The plan comes from codex app-server, the program the ChatGPT app and the editor extension use to talk to Codex. Xenon starts its own copy only while the tile is on a dashboard, asks it only to read, and closes it a few minutes after it is no longer needed.

The hooks report to 127.0.0.1, your own PC, with a key Xenon created. Xenon refuses any report without it, and the key is read from Xenon’s own data folder, so it never appears on a command line. Live session state is kept in memory and starts empty when Xenon restarts.

Widgets you install can read the plan numbers through the codex stream, if you allow it: percentages, window lengths, token counts and how many sessions are working. Never a folder, a project, a conversation, a command or your email.

Common questions

Can I see my Codex usage limits on a second screen?

Yes. With Codex installed and signed in, the tile shows each usage window of your plan with how much is used and a countdown to its reset. Connecting Codex is not needed for this.

Does it work with the ChatGPT desktop app?

The plan, the usage and the conversation list cover Codex in the ChatGPT app, the editor extension and the codex command, because they share the same account and engine. Live sessions and approvals need Codex to run hooks, which the codex command does.

What happens if I do not answer a request?

Nothing is approved. After 90 seconds, or if Xenon is closed, the request goes back to Codex, which asks you as usual.

Why do I have to trust the hooks in Codex?

Codex runs a hook only after you have trusted that exact hook. It is Codex’s own safety check, so Xenon never does it for you. If Xenon or Node moves to another folder, the hooks change and Codex asks you to trust them again; the tile says when.

Does the tile work with an API key?

Sessions and approvals do. The plan windows exist only on a ChatGPT plan, so with an API key the tile has none to show.