wavever/CCLimitPing
wavever/CCLimitPing has 60 GitHub stars and 12 forks. GitHot measured 0 in 7 days and 0 in 15 days. Last checked 2026-11-15 15:32 UTC. Last push 2026-11-03.
What you can do
- ⏱️ Back-to-back windows — pings each provider right after reset, via the official CLI.
- 🧠 Never interrupts you — CLI hooks detect an active session and let it start the window itself.
- 🌙 Auto-continue overnight tasks — limitping continue codex types "continue" the moment the limit recovers (Unix only; it needs a PTY).
- 📊 Real token & cost numbers — today / week / month, from local session transcripts.
Measured star growth
- in 24h
- Update delayed
- in 7 days
- 0
- in 15 days
- 0
- in 1 month
- Update delayed
Net star changes over overlapping periods, not daily totals. Missing measurements are left blank. Stars measure attention, not software quality.
About
Keep your Claude Code / Codex 5h rate-limit windows back-to-back — auto-pings each provider the moment its window resets. | 在 5 小时限额窗口重置的瞬间自动触发计时,让 Claude Code / Codex 的窗口背靠背、不留空档。
Developer ToolsREADME.md
Original
CCLimitPing
Never waste a minute of your Claude Code / Codex 5-hour window.
limitping starts your next rate-limit window the instant the last one resets — automatically.
English · 中文
The problem
A new 5h window only starts when you send your first billable request — not when the old one resets. Come back 2 hours late and those 2 hours are gone, and your schedule drifts.
Without limitping |====== 5h ======|..... idle 2h .....|====== 5h ======|
With limitping |====== 5h ======|====== 5h ======|====== 5h ======|
↑ auto-ping at reset
Quick start
curl -fsSL https://raw.githubusercontent.com/wavever/CCLimitPing/main/install.sh | sh
limitping status # see your 5h / weekly usage and reset countdown
limitping bg start # keep windows back-to-back in the background
Single binary, no Go required. Uses your existing claude / codex login — no new credentials, no telemetry.
Want to look before it spends quota? limitping ping --dry-run.
Highlights
- ⏱️ Back-to-back windows — pings each provider right after reset, via the official CLI.
- 🧠 Never interrupts you — CLI hooks detect an active session and let it start the window itself.
- 🌙 Auto-continue overnight tasks —
limitping continue codextypes "continue" the moment the limit recovers (Unix only; it needs a PTY). - 📊 Real token & cost numbers — today / week / month, from local session transcripts.
- 🎟️ Don't lose reset credits — lists Codex reset credits and Claude reset cards; optional
auto_redeembefore expiry. - ⌨️ Short to type — every command works as
lmp(lmp s,lmp w).
| Provider | Read usage (zero-quota) | Trigger | Auth |
|---|---|---|---|
| Claude Code | …/api/oauth/usage |
interactive Claude Code CLI | OAuth (Keychain / ~/.claude) |
| Codex | …/backend-api/wham/usage |
codex exec --ephemeral |
OAuth (~/.codex/auth.json) |
What a ping actually runs, and how usage is read without starting a window: How it works.
Docs
- How it works — what a ping sends, and how usage is read
- Install, upgrade, and uninstall
- Commands — full command list, aliases, and
lmp - Status, tokens, and cost
- Configuration
- Active-session hooks
- Scheduled pings
- Background watch
- Auto-continue
- Cost and caveats
- Layout and releasing
Privacy · Security · Contributing · Code of conduct
License
MIT © wavever