Merencanakan penggunaan kuota mingguan OpenAI Codex dengan memprediksi extra reset dan mengelola banked resets melalui berbagai strategi penggunaan.
Juga dikenal sebagai ItsOdeLeo/codex4ever
- Stars
- 5
- Tools
- —
- Unduhan, 30 hari
- —
- Versi terbaru
- 0.1.3
- Commit terakhir
- 29 Okt 2026
- Lisensi
- MIT
Apa itu Usage Planner MCP?
Usage Planner adalah MCP server. Merencanakan penggunaan kuota mingguan OpenAI Codex dengan memprediksi extra reset dan mengelola banked resets melalui berbagai strategi penggunaan.
Ringkasan dibuat dari README proyek
Tentang Usage Planner MCP server
Codex4ever, yang sekarang dikenal sebagai Usage Planner, membantu developer mengelola kuota mingguan OpenAI Codex mereka. Tool ini menyediakan timeline dua minggu yang melacak penggunaan harian, sisa kuota, dan potensi titik habisnya kuota. Tool ini dirancang untuk pengguna yang ingin memprediksi kapan kuota mereka akan habis dan memutuskan kapan harus menggunakan banked resets. Tersedia lima strategi berbeda, termasuk Keep pace, Keep available, Use it all, Weekdays only, dan Weekend focus.
Anda dapat mengakses planner ini melalui website berbasis browser, plugin Codex, atau sebagai MCP server untuk client seperti Claude Desktop dan Cursor. Saat menggunakan MCP server atau plugin, sistem akan membaca data kuota lokal yang sudah signed-in dari Codex CLI di mesin yang sama, sehingga tidak memerlukan API keys tambahan. Engine prediksi menggunakan riwayat reset publik untuk memprediksi extra resets dengan probabilitas minimal 60%, dengan penempatan waktu yang konservatif untuk memastikan keandalan.
Apa yang bisa Anda lakukan dengannya
- 1Prediksi habisnya kuotaTentukan secara tepat kapan tingkat penggunaan Anda saat ini akan menyebabkan kuota Codex Anda habis.
- 2Prediksi extra resetsEstimasi kemungkinan dan waktu terjadinya reset otomatis dalam 48 jam ke depan.
- 3Terapkan strategi penggunaanSesuaikan perencanaan Anda berdasarkan kebutuhan spesifik, seperti hanya menggunakan layanan pada hari kerja.
Ditulis berdasarkan README proyek. Setiap use case diperiksa terhadap kutipan dari README tersebut.
Cara menginstal Usage Planner MCP
Format diverifikasi 10 Nov 2026Instal Usage Planner MCP di Claude Code
$ claude mcp add codex4ever -- npx -y codex4everInstal Usage Planner MCP di Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"codex4ever": {
"command": "npx",
"args": [
"-y",
"codex4ever"
]
}
}
}Instal Usage Planner MCP di VS Code
.vscode/mcp.json
{
"servers": {
"codex4ever": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"codex4ever"
]
}
}
}Instal Usage Planner MCP di Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"codex4ever": {
"command": "npx",
"args": [
"-y",
"codex4ever"
]
}
}
}Instal Usage Planner MCP di Codex
~/.codex/config.toml
[mcp_servers.codex4ever] command = "npx" args = ["-y", "codex4ever"]
Instal Usage Planner MCP di Gemini CLI
~/.gemini/settings.json
{
"mcpServers": {
"codex4ever": {
"command": "npx",
"args": [
"-y",
"codex4ever"
]
}
}
}Pengecekan otomatis
Berjalan 13 Nov 2026Laporan lengkap →Lolos checks otomatis kami. Ini bukan audit keamanan: baca kodenya dan berikan server akses paling terbatas yang dibutuhkannya. Cara kerja checks
- Source repository terhubung dan dapat dijangkauitsodeleo/codex4ever is public and reachablegithub.com/itsodeleo/codex4ever ↗Lolos
- Paket menyebut repo ini sebagai sumbernyacodex4ever names itsodeleo/codex4ever as sourcenpmjs.com/package/codex4ever ↗Lolos
- Provenance build (atestasi Sigstore)No build attestation published for this releaseTidak diperiksa
- Lisensi open source (OSI)MITspdx.org/licenses/MIT.html ↗Lolos
- Ada commit atau release dalam satu tahun terakhirLast commit or release 2026-10-29github.com/itsodeleo/codex4ever ↗Lolos
- OpenSSF ScorecardTidak diperiksa
- Nama package tidak mirip dengan package populerNo popular package one edit away from codex4everLolos
- Tidak ada advisory kritis di paket maupun dependensinya1 resolved dependencies checked; no critical advisoryosv.dev ↗Lolos
- Tidak ada instruksi tersembunyi untuk model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersLolos
- Tools yang bersifat destruktif telah diberi labelTidak diperiksa
- Endpoint remote menjawab handshake MCPTidak diperiksa
README
Lihat di GitHubUsage Planner — Codex quota & reset planner
Usage Planner (formerly Codex4ever) is a planner for your OpenAI Codex weekly quota. It shows when your quota runs out at your current pace, whether a predicted extra reset is likely to arrive first, and when a banked reset is worth redeeming.
Unofficial; not affiliated with OpenAI. MIT licensed.
Pick a strategy
Ask once in Codex and the planner opens beside the chat. Pick a strategy and the plan changes: daily usage, refills and run-out points.
What it does
- Timeline of your next two weeks — daily usage, remaining quota, run-out points, outages, normal refreshes and banked-reset uses, one column per day.
- Extra-reset forecast — the chance of an automatic reset in the next 48 hours, the likely window, and a second reset conditioned on the first, built from public reset history and Tibo's public posts.
- Five strategies — Keep pace (your current pace: see when quota runs out), Keep available, Use it all (empty quota just before the next refill), Weekdays only, Weekend focus.
- Codex plugin — reads your local, signed-in quota and banked resets, plans in the conversation, and opens the same visual planner.
How it plans
- A predicted reset is counted only when it is at least 60% likely before the refresh in effect, and it is placed at a conservative time (where it has most probably already happened), not at its single most likely hour. You can switch the count to 0, 1 or 2 on the timeline.
- Every refill restarts the seven-day window — a banked reset, an extra reset or the normal refresh.
- Banked resets: extras cover outages, earliest expiry first; the last one is kept for a real outage (24 h or more), and a bank about to expire can be used rather than wasted.
- One rule everywhere: the website, the plugin page and the plugin's MCP tools always give the same plan for the same inputs.
The forecast is an uncalibrated model estimate, not a promise. Usage Planner never redeems a reset or spends credits for you.
Use it
Codex plugin (Node.js 20+ and a signed-in Codex app or CLI):
codex plugin marketplace add ItsOdeLeo/usage-planner
codex plugin add usage-planner@usage-planner
Start a new Codex chat and ask: "Open quota planning." Reading your quota is local and read-only; no separate API key is needed.
Other MCP clients (Claude Code, Claude Desktop, Cursor and others): the same server is on npm as usage-planner and in the MCP Registry as io.github.ItsOdeLeo/usage-planner. Reading your quota still needs a signed-in Codex CLI on the same machine.
{ "mcpServers": { "usage-planner": { "command": "npx", "args": ["-y", "usage-planner"] } } }
Website: usageplanner.com, no install. Enter your quota by hand; everything is calculated in your browser and your inputs are not sent anywhere.
Run locally:
npm install
npm run web # http://127.0.0.1:4173/
npm test
Data sources
Public reset data comes from Codex Resets, including the bundled offline archive (npm run archive:refresh). Thanks to its maintainer. With an optional X API token, Tibo's full timeline is read directly from X.
Development
| Command | What it does |
|---|---|
npm run web |
Local site with live reset evidence (cached 30 minutes) |
npm run site:build |
Static site in dist/, evidence collected at build time |
npm run plugin:build |
Self-contained Codex plugin in plugins/usage-planner/ |
npm run mcp |
MCP server from source |
npm run backtest:public |
Day-by-day replay of the forecast against public history |
.github/workflows/deploy-site.yml rebuilds the static site every 30 minutes and deploys it to Cloudflare Pages. Optional settings (LLM classification of posts, X timeline access) are listed in .env.example; keys are only read at build time and never reach the browser.
Design and algorithm details: docs/technical-notes.zh.md (Chinese).
中文简介
Usage Planner(原名 Codex4ever)是 OpenAI Codex 每周额度的本地规划器:按你当前的速度显示额度什么时候用完、额外 reset 是否可能先到,以及备用 reset 什么时候值得用。预测的 reset 只在“正常刷新前发生的概率 ≥ 60%”时计入,并放在保守时刻;任何一次补满都会重新开始 7 天周期;备用默认至少保留一个。网页、插件页面和插件的 MCP 工具始终使用同一套规则。非官方工具,与 OpenAI 无隶属关系。详细设计见 技术说明。
Author
Built by 欧的Leo — @ItsOdeLeo on X · 小红书 ItsOdeLeo. Feedback and ideas are welcome there or in GitHub issues.
Pertanyaan tentang Usage Planner MCP
Bagaimana cara menambahkan Usage Planner MCP ke Claude Code?
Jalankan claude mcp add codex4ever -- npx -y codex4ever di terminal Anda. Tambahkan --scope user agar tersedia di semua proyek.
Bagaimana cara menambahkan Usage Planner MCP ke Cursor?
Buka ~/.cursor/mcp.json dan tambahkan server di bawah mcpServers, menggunakan config Cursor yang ditunjukkan di bagian instalasi di atas.
Bagaimana cara kerja prediksi extra-reset?
Sistem menghitung peluang reset otomatis dalam 48 jam ke depan berdasarkan riwayat reset publik dan postingan media sosial, dan hanya akan menghitungnya jika probabilitasnya minimal 60%.
Strategi penggunaan apa saja yang tersedia?
Planner ini menawarkan lima strategi: Keep pace, Keep available, Use it all, Weekdays only, dan Weekend focus.