Divoom blog banner

How a Divoom Times Gate Became a Codex and Claude Code Usage Tracker

Written by Divoom Professional Team

Updated on

Thank you to opezdol for sharing their Times Gate dashboard and the photo of it in use. With usage numbers for Codex and Claude Code already available on their computer, they wanted a way to see them on the desk. They turned the frame’s five screens into a dashboard for usage limits, reset times, estimated costs, and coding-session status.

A Codex and Claude Code usage tracker on Divoom Times Gate
by u/opezdol in r/codex

Why the Numbers Moved to the Desk

Opezdol used Codex and Claude Code and chose to put the figures from both tools on one desk display. The layout brings information that changes throughout a work session into a place they can check without opening another window.

The five screens made it possible to give the two services separate places while keeping a shared view of their activity in the center. The display sits above a monitor in the creator’s photo, within the same sightline as the work.

The project started with usage and approximate cost information from CodexBar, a menu bar app. Opezdol’s contribution was to carry that information onto the desk and decide which figures belonged together on each screen.

What Goes on the Five Screens

In the project photo, the outer left screen and the screen immediately right of center show limits. They group session and weekly figures with reset information. Putting the remaining amount and its reset on the same screen gives the percentage a time frame.

The second screen from the left and the far-right screen show cost and token figures, with separate views for the session and the last 30 days. The repeated layout makes it easier to look for the same kind of number on either side.

The center screen is labeled Status. It lists Codex and Claude and shows their state at the moment the photo was taken. That placement gives activity a place of its own between the two sets of numbers.

Opezdol’s Times Gate above a monitor showing five panels for Codex and Claude Code limits, costs, and status
Opezdol’s Times Gate puts a shared status screen between two sets of limits and cost figures. Photo by opezdol.

How the Data Reached the Times Gate

Opezdol described a path that starts at CodexBar, where they obtained the usage figures and approximate costs. A server they operated received those values and passed the updates through a Divoom API.

The last step pushed the data to the device on the local network. In their build, the screen was the destination for the summary. The services and the software collecting their data stayed elsewhere.

The Times Gate API developer guide provides background on custom display integrations. Opezdol’s dashboard was a community project that combined that display capability with a separate source of coding usage data.

How to Read Limits, Usage, and Cost

Each type of number answers a different question. A limit figure gives the remaining allowance within a time window. A reset time gives that figure an endpoint. At a glance, those two values explain more together than a percentage alone.

Cost and token figures use a different frame of reference. They describe estimated activity over the session or a longer lookback. The creator called the costs approximate, so they are useful as a record of scale in this setup rather than a definitive account charge.

The center screen answers a shorter-term question about current activity. In the photo, one tool is working and the other is idle. That distinction explains why the project gives status its own screen instead of folding it into either cost panel.

What Was Still a Work in Progress

Opezdol said the tracker worked in the setup they showed. They still wanted to remove the local-network dependency, which remained part of the path delivering updates to the device.

That is an important detail about the role of the remote server. It handled one step in the chain. Delivery to the frame still relied on a local push in the version the creator described.

The photo is a record of the dashboard in use at that stage. It shows which readings the creator chose to surface and where they put them. Their description leaves the update frequency and a future remote-only setup open.

FAQ About the Usage Tracker

Which Divoom model did opezdol use?

They used the Divoom Times Gate, the model with five small LCD screens arranged side by side.

Where did the usage and cost numbers come from?

Opezdol sourced the figures from CodexBar. The dashboard includes estimated costs, and the labels in the photo distinguish session figures from the longer lookback.

Could the dashboard update away from the local network?

The version they shared still used a local device push. Removing that dependence was a change they wanted to make later.

Conclusion

Opezdol turned an existing set of coding-tool figures into something they could read above their monitor. The useful design choice was giving limits, estimated costs, and activity predictable places on the display.

The Divoom Times Gate fits a desk where several small views need to be visible together. Its five LCD screens give each view a defined place. In this setup that meant two pairs of usage panels around a shared status screen, with the data supplied by the creator’s own integration.

Affichage d'Informations Pixel Art Divoom Times Gate avec 5 Écrans LCD Intelligents Divoom Times Gate pixel art info display with 5 smart LCD screens. Live stats, clocks, weather, calendar, crypto tickers, and custom pixel animations. $103.99 USD $139.99 USD avec le code BF26GATE Buy now

Disclaimer: This content is for general information only and is not professional or medical advice, a safety guarantee, or permission to use third-party intellectual property. Follow official product instructions and obtain any required permissions before attempting DIY projects or modifications.

Editor's Recommendation