Kyle is Based v0.2.2
Make every percent count
From the developer
Not specified in the available declarations: limitations, pricing & account requirements.
Developer declarations; not independently tested. Listing last checked Nov 14, 2026. Package observed Nov 14, 2026.
From the marketplace listing
Track your own Codex allowance with a clean local dashboard, reset-aligned Day/Week views, a fixed 100%-to-0% target, saved history, and an optional announced-reset planning override. Dotted lines show changes between observations across offline gaps; their exact timing is unknown. Requires desktop execution, Node.js 22+ and Codex CLI signed in with ChatGPT. Start with “Start Orbit”. It checks usage every minute even with the dashboard closed. History survives restarts and is separated by account. Windows users can explicitly enable automatic startup at sign-in and background recovery with “Enable Orbit startup”, or remove it with “Disable Orbit startup”. Startup is off by default. Usage stays on your computer. No cloud upload, phone synchronization or API billing. The computer must be awake and online for fresh readings. Tested on Windows; macOS/Linux not verified. Independent companion, not affiliated with OpenAI.
Language: English · Automatically detected from descriptions.
Exact text from the indicated source. A mention alone does not establish support for your task.
Track your own Codex allowance with a clean local dashboard, reset-aligned Day/Week views, a fixed 100%-to-0% target, saved history, and an optional announced-reset planning override. Dotted lines show changes between observations across offline gaps; their exact timing is unknown. Requires desktop execution, Node.js 22+ and Codex CLI signed in with ChatGPT. Start with “Start Orbit”. It checks usage every minute even with the dashboard closed. History survives restarts and is separated by account. Windows users can explicitly enable automatic startup at sign-in and background recovery with “Enable Orbit startup”, or remove it with “Disable Orbit startup”. Startup is off by default. Usage stays on your computer. No cloud upload, phone synchronization or API billing. The computer must be awake and online for fresh readings. Tested on Windows; macOS/Linux not verified. Independent companion, not affiliated with OpenAI.
Track your own Codex allowance against a fixed weekly target, with a live local dashboard and saved history.
codex usage pacing productivity
· 3 observations
Plugin name changed from “Pace” to “Orbit | Weekly Usage Maximizer”. Brand color changed from “#A38AFF” to “#8A6A32”. Default prompt removed: “Start Pace and show my weekly usage dashboard.”. Default prompts updated; open the comparison for details. 5 more changes in the comparison.
View comparison →Package or technical metadata updated
View technical comparison →Find competitors to follow as you develop your plugin.
Plan short stays with a rolling 90/180 day counter.
Shared terms: count, planning, remove, reset
Token Weather scalar budget planning with optional local Codex weather, event replay and checkpoints.
Shared terms: count, automatic, local, optional
Animated local Codex usage and API-equivalent cost dashboard
Shared terms: api, dashboard, local, maco
Runs a local Windows x64 title-bar HUD for Codex usage and public reset status.
Shared terms: cloud, companion, desktop, linux
Connect your paired computers to ChatGPT through Desktop Alsalibi.
Shared terms: background, companion, computer, desktop
--- name: orbit description: Start, view, or stop the Orbit desktop usage tracker; compare the signed-in Codex account's remaining allowance with its full-period target and review recorded history. Requires local desktop execution. Not API billing or phone/cloud synchronization. --- # Orbit Resolve `../../scripts/pace.mjs` relative to this skill folder. It is the plugin's bundled controller; run it with Node.js 22+ and one argument: `start`, `status`, `stop`, `enable-startup`, or `disable-startup`. Use a properly quoted absolute path. The script locates the user's Codex CLI and reads its signed-in ChatGPT account. Do not read credential files or ask for tokens. For “start Orbit”, setup, or opening the dashboard, run `start`. This starts a background local tracker that reads usage every minute until stopped or the computer shuts down. Explain that behavior briefly, then open its returned loopback URL in the available browser. If browser opening isn't available, provide the URL. Never substitute the publisher's private Orbit website. For a pacing or usage question, run `status` once. If stopped, say so; do not start ongoing tracking merely to answer a one-time question. If running with a fresh reading, use returned bucket values and reset time. Target remaining is `100 × clamp((reset − now)/(windowMinutes × 60000), 0, 1)`. Target used is 100 minus target remaining. Compare actual remaining minus target remaining in percentage points. The target always runs from 100% at the window's start to 0% at reset, independent of the current balance or optional reserve. Separate measured values from calculated targets. State source time and any stale/error status. For “stop Orbit”, run `stop`; this preserves recorded history. Do not remove histories unless the user asks. Updates record actual observations only, account-separated on the user's computer. Missing time is not reconstructed. History and preferences are not synchronized to phones or other computers. If Node.js or Codex CLI is missing, explain the missing prerequisite. Follow the host's installation rules; do not silently install or sign in. If no ChatGPT account is signed in, ask the user to sign in through the normal Codex CLI flow, then try again. Never run a prompt, consume reset credits, change accounts, publish data, or alter the user's hosted website as part of this skill. This is a local companion for personal account usage. Do not claim commercial integration approval or hosted access. On hosts without local execution, explain that the desktop plugin is required. ## Optional Windows startup Only when the user explicitly asks to start Orbit automatically after restart/sign-in, run `enable-startup`. Explain that this installs a per-user Windows Startup launcher and copies the runtime into the PacePlugin data folder. It checks usage with the dashboard closed and recovers when the tracker exits. No administrator access is required. Startup is off by default. Do not enable it merely for a normal Start Orbit request. Run `disable-startup` when asked to remove automatic startup. This removes the launcher; it does not delete history or stop an already running tracker. Use `stop` too when the user asks to stop tracking. Stop pauses tracking until Start Orbit or the next Windows sign-in if startup remains enabled. No startup support is claimed for macOS/Linux. Day shows consecutive 24-hour blocks anchored to the usage reset. Week shows the full period. Dotted blue connectors show the change between real readings across gaps, not measured usage timing. Never describe interpolated lines as actual historical observations.
--- name: pace description: Start, view, or stop the Pace desktop usage tracker; compare the signed-in Codex account's remaining allowance with its full-period target and review recorded history. Requires local desktop execution. Not API billing or phone/cloud synchronization. --- # Pace Resolve `../../scripts/pace.mjs` relative to this skill folder. It is the plugin's bundled controller; run it with Node.js 22+ and one argument: `start`, `status`, or `stop`. Use a properly quoted absolute path. The script locates the user's Codex CLI and reads its signed-in ChatGPT account. Do not read credential files or ask for tokens. For “start Pace”, setup, or opening the dashboard, run `start`. This starts a background local tracker that reads usage every minute until stopped or the computer shuts down. Explain that behavior briefly, then open its returned loopback URL in the available browser. If browser opening isn't available, provide the URL. Never substitute the publisher's private Pace website. For a pacing or usage question, run `status` once. If stopped, say so; do not start ongoing tracking merely to answer a one-time question. If running with a fresh reading, use returned bucket values and reset time. Target remaining is `100 × clamp((reset − now)/(windowMinutes × 60000), 0, 1)`. Target used is 100 minus target remaining. Compare actual remaining minus target remaining in percentage points. The target always runs from 100% at the window's start to 0% at reset, independent of the current balance or optional reserve. Separate measured values from calculated targets. State source time and any stale/error status. For “stop Pace”, run `stop`; this preserves recorded history. Do not remove histories unless the user asks. Updates record actual observations only, account-separated on the user's computer. Missing time is not reconstructed. History and preferences are not synchronized to phones or other computers. If Node.js or Codex CLI is missing, explain the missing prerequisite. Follow the host's installation rules; do not silently install or sign in. If no ChatGPT account is signed in, ask the user to sign in through the normal Codex CLI flow, then try again. Never run a prompt, consume reset credits, change accounts, enable startup tasks, publish data, or alter the user's hosted website as part of this skill. This is a local companion for personal account usage. Do not claim commercial integration approval or hosted access. On hosts without local execution, explain that the desktop plugin is required.
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
Package observed Nov 14, 2026.
plugins_6aeb9ffb2a0081918fb67459d8f94494
Download plugin data (JSON)Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.
