Launch
QuotaWake
Visit
Example Image

QuotaWake

macOS menu bar app for AI coding session readiness

Visit

QuotaWake is an open-source macOS menu bar app for AI coding session readiness and usage-window scheduling. It keeps Claude Code and Codex CLI workflows ready around planned usage windows, runs local-first, stores no provider tokens, and keeps readiness logs on your Mac. MIT-licensed.

Example Image
Example Image
Example Image
Example Image

Features

Local-first macOS menu bar app

Uses the official Claude Code and Codex CLIs

No provider tokens stored, no provider HTTP requests

Usage-window scheduling and readiness logs kept locally

MIT-licensed open source

Use Cases

Keep Claude Code and Codex CLI sessions ready around usage windows

Plan local AI coding readiness without manual intervention

Review readiness logs locally on your Mac

Comments

custom-img
DevOps x AI | SRE | AWS | Python

Nice one! Will try that

custom-img
DevOps x AI | SRE | AWS | Python

Nice one! Will try that

Ohh nice :) I'd like to take look at that! amazing

Ohh nice!, I'd like to take look at that!

custom-img
I want to make life easy.

wow, nice looking website.

I built QuotaWake to keep my Claude Code and Codex CLI sessions ready around usage windows without babysitting the terminal. It is local-first, MIT-licensed, stores no provider tokens, and keeps logs on my Mac. Feedback from fellow devs is very welcome.

custom-img
We build clean, intuitive digital tools ...

cOOL one Let me look at that

custom-img
Marketing

This feels like one of those small tools that solves a very annoying daily problem. I like that it sits in the menu bar and doesn’t try to become a big dashboard. For Claude Code / Codex users, just knowing when a session is ready again is enough. Also, the local-first approach makes sense here — I wouldn’t want to connect tokens or send extra requests just for this. One thing I’d love to see is a simple history view, like when the session became ready and when I missed it.

custom-img
Founder- Quantara

Local-first + no provider tokens stored is a good trust signal for a tool that's literally watching your Claude Code/Codex usage. How does it detect the usage window without hitting the provider's API? polling local session state, or something else?

custom-img
Founder at Plantory

Running multiple Claude Code sessions daily, the usage-window reset is exactly what I keep checking by hand, so this scratches a real itch. Local-first with no provider tokens is the right call — reading the official CLI state instead of hitting APIs means nothing new to trust. Does it handle multiple accounts/profiles on one Mac? MIT license is a nice touch.

Premium Products
View all
Example Image
Awards
View all
Example Image

Comments

custom-img
DevOps x AI | SRE | AWS | Python

Nice one! Will try that

custom-img
DevOps x AI | SRE | AWS | Python

Nice one! Will try that

Ohh nice :) I'd like to take look at that! amazing

Ohh nice!, I'd like to take look at that!

custom-img
I want to make life easy.

wow, nice looking website.

I built QuotaWake to keep my Claude Code and Codex CLI sessions ready around usage windows without babysitting the terminal. It is local-first, MIT-licensed, stores no provider tokens, and keeps logs on my Mac. Feedback from fellow devs is very welcome.

custom-img
We build clean, intuitive digital tools ...

cOOL one Let me look at that

custom-img
Marketing

This feels like one of those small tools that solves a very annoying daily problem. I like that it sits in the menu bar and doesn’t try to become a big dashboard. For Claude Code / Codex users, just knowing when a session is ready again is enough. Also, the local-first approach makes sense here — I wouldn’t want to connect tokens or send extra requests just for this. One thing I’d love to see is a simple history view, like when the session became ready and when I missed it.

custom-img
Founder- Quantara

Local-first + no provider tokens stored is a good trust signal for a tool that's literally watching your Claude Code/Codex usage. How does it detect the usage window without hitting the provider's API? polling local session state, or something else?

custom-img
Founder at Plantory

Running multiple Claude Code sessions daily, the usage-window reset is exactly what I keep checking by hand, so this scratches a real itch. Local-first with no provider tokens is the right call — reading the official CLI state instead of hitting APIs means nothing new to trust. Does it handle multiple accounts/profiles on one Mac? MIT license is a nice touch.

Premium Products