HELP & SUPPORT
Get it working,
right at hand.
Installation, usage and troubleshooting for Codex Quota Key.
01 / Before installation
Marketplace submission is being prepared. There is no official Marketplace download yet. This page does not indicate Logitech approval.
- Check your device and environment
The current target is Windows with MX Creative Keypad and a running installation of Logi Options+. Untested devices and Mac are outside the supported scope.
- Set up Codex CLI
Follow the official OpenAI guide to install and sign in to Codex CLI. The plugin queries quota through the CLI; you do not need to send passwords or API keys to the author.
- Install the plugin
Use the Marketplace install link after release. If the author provides a test .lplug4 package, open it with Logi's plugin installer. A test installation does not imply Marketplace approval.
- Add your keys
In Options+, find All Actions → Codex Quota Key → CODEX tools and drag the actions you need to unused keys. You do not need to replace your existing profile.
02 / How to use it
The outer key shows quota and overall status. Press to expand; Logitech provides the top-left back key. The right column opens conversations, the pinned conversation, and a separate pet page. The four quota keys keep their layout.
Select a conversation for details and pinning. Open Codex in its details targets that conversation. Navigation with the app running is verified; cold start remains untested. Choose Chinese, English or Japanese in plugin settings.
The standalone quota overview offers an optional double-click to open Codex. The dashboard entry is managed by Logi and does not offer the same double-click behavior.
03 / Frequently asked questions
Why does quota differ from the desktop app?
The plugin uses the account signed in to Codex CLI. If the desktop uses another account, quota can differ. Check the accounts, then press the quota key to query again.
Why does it show Unknown or an outlined dot?
Live status requires the running Codex desktop app and a compatible local protocol. A missing connection, incompatible protocol or unavailable conversation snapshot produces Unknown, not a guessed idle state. CLI quota queries work independently.
Why are ordinary ChatGPT chats missing?
Only local Codex conversations are supported, excluding regular ChatGPT cloud chats and remote sessions. Up to 32 unarchived local conversations are monitored, with the pinned conversation prioritized.
Why do the numbers in the editor stay the same?
Options+ may cache its key previews. Check the physical key and compare values before and after opening the panel. If the device also fails to update, check CLI sign-in, network access and the Logi service.
What do the colors mean?
Outer quota number and progress bar: green above 30%, yellow at 10–30%, red below 10%; exhausted weekly quota also turns red. Status dots: blue running, yellow waiting for input or approval, red failed, green ready to review, gray idle or stopped, hollow unknown.
What remains after uninstalling?
Uninstall through Logi plugin management. The local CodexQuotaKey data folder may retain quota cache, pinned conversation ID, pet settings and cached assets, and status diagnostics. Remove these if desired, but keep the .codex folder containing Codex data.
04 / Help me reproduce the issue
Reply to the author's release post where you found the plugin, with the details below. The author's GitHub account is fuxiyc (七月七夕) ↗. A dedicated issue repository is not available yet.
Plugin version: Windows / Logi Options+ version: Device model: Steps to reproduce: Expected result: Actual result: Does it occur on the physical key, or only in the editor preview?
Do not include account credentials, auth.json, full chat logs or screenshots of private conversations. Share only the minimum information needed to explain the issue.