QuotaCrew for Codex — auto-switch accounts, resume chats, and shut down your PC when work is done

erkandev — Thu, 12 Nov 2026 11:15:28 +0000

QuotaCrew is a free, open-source Windows app available on the Microsoft Store. I built it to switch Codex accounts automatically when quota runs out, help resume interrupted work in the same conversation, and optionally shut down my PC when the job is done.

I'd leave Codex working on a task, come back later, and find it stuck at a usage limit. Then I'd check which account still had quota, switch over, and find the conversation I wanted to resume. I wanted to handle those steps in one place.

Switching accounts when quota runs out

I wanted to see which accounts had room before touching the active session. The dashboard compares remaining quota and reset times for the five-hour and weekly windows. When automatic switching is enabled, QuotaCrew checks the destination account before switching. You can also switch manually or require confirmation. A switch restarts Codex Desktop.

Figuring out whether the conversation actually resumed

The interesting problem came after the switch. A different account can be active while the old conversation is still idle. QuotaCrew's Jobs view shows the continuation request and the observed result separately.

For supported Desktop or local VS Code conversations, QuotaCrew can ask Codex to continue in the same chat. Some Desktop goal conversations can resume just by opening them. If a request might have reached Codex but its outcome is unclear, QuotaCrew watches for a new turn and avoids sending the request again automatically. Automatic continuation is experimental and depends on the installed Codex version. Continuation design

Shutting down after a job finishes

I also wanted to stop waiting at my desk just to turn the PC off. I can choose a conversation and confirm a shutdown plan. It waits until that task finishes and other observed Codex work has stopped, then starts a two-minute countdown I can cancel. If QuotaCrew can't verify the work has stopped, the shutdown stays on hold.

I'm curious how other Windows developers deal with interrupted Codex sessions. What would you want to see before trusting a tool to pick up the same conversation? Source code

English adaptation with AI assistance.

DEV Community: erkandev

QuotaCrew for Codex — auto-switch accounts, resume chats, and shut down your PC when work is done

Switching accounts when quota runs out

Figuring out whether the conversation actually resumed

Shutting down after a job finishes