LimitPing – Keep Claude Code and Codex rate-limit windows continuous
Keeps AI coding quota windows back-to-back so you stop wasting paid rate limits.
Respect-weighted rate limits for the open web
Uses cryptographic device-continuity proof instead of CAPTCHA for rate limiting.
Web developers, API maintainers
Privacy Pass · Cloudflare Turnstile · Anubis
continuity-auth is my attempt to fix this from first principles by using device-continuity proof as a trust signal and time (enforced via rate-limiting) as the core resource to provide a graceful, zero-trust, login-less method to prevent abuse, supporting both browsers and CLI as first-class clients.
Built with Clojure/Script, babashka, and Datalevin. Work in progress. Happy to discuss.
Keeps AI coding quota windows back-to-back so you stop wasting paid rate limits.
Seamlessly hand off Claude Code sessions to Gemini without losing 30 messages of context.
Weight-based formula beats flat 400mg guidelines for personalized safety limits.
Shows all four Claude limits (Session, Weekly, Weekly Sonnet, Overage) in one widget with color-coded warnings and reset countdowns — exactly the tiny UX gap heavy users kept bumping into. The author went native: Swift + WidgetKit, OAuth PKCE (no API keys), App Group UserDefaults for widget/app sync and a Homebrew tap for install — practical choices that make this something you'd actually run on your desktop. Limited to macOS Sonoma and Claude subscribers, so great for the audience but narrow in reach.
Single component replaces nginx + auth + monitoring for exposed Ollama instances.
Zero-dep PowerShell tray app beats checking /usage mid-refactor.