Troubleshooting

Find the symptom below. Check the current Stable download and, after installing or updating, open QuotaMew from Applications. You do not need to delete settings, runtime files or authentication data.

QuotaMew does not appear

Symptom and likely causes: There is no Dock window or visible menu-bar item. QuotaMew is a menu-bar app; its item may be disabled or hidden by limited space or macOS visibility controls.

Safe checks: Look in the menu bar, including any overflow manager you use. Open QuotaMew from Applications to access its available recovery/settings UI. In Settings → General, check Show Menu Bar Item. If macOS requires visibility approval, follow the app's message.

Next action: If it still does not appear, quit the running copy through its available menu/UI and reopen it. Report the app and macOS versions if it persists. Do not run multiple downloaded copies.

App cannot be opened

Symptom and likely cause: macOS blocks a newly installed or updated copy. Current distribution signing may require individual app approval.

Safe checks: Confirm the download came from this site or the official GitHub Release, and that you moved it to Applications. Follow the First Launch guide, including System Settings → Privacy & Security → Open Anyway only when you trust the source.

Next action: If the message says the app will damage your computer or has been modified, stop and check the download source instead of bypassing it. For other persistent launch failures, report the exact non-sensitive message and version. Keep system security protections enabled.

No Codex quota is shown

Symptom and likely causes: Codex is missing, disabled, not installed, or not configured. The local runtime may be missing or undiscoverable, or Codex may not be signed in.

Safe checks: Follow Codex prerequisites. Enable Codex in Settings → Providers, confirm the coding tool can sign in on its own, and select Refresh Now from QuotaMew's right-click menu. A browser session or terminal alias alone is not a local runtime.

Next action: Check Settings → General → Diagnostics for runtime and connection state. Copy the built-in report if you need help; do not copy credentials or raw runtime output.

Quota appears unavailable

Symptom and likely causes: A provider card shows unavailable/failed, or a quota displays a dash. The runtime response, authentication mode or quota window may not be supported. A missing quota is not zero remaining.

Safe checks: Read the provider status and Diagnostics, confirm Codex itself works, and refresh once. If only Luna Reserve is missing, it may simply not have been reported; selecting it does not activate it.

Next action: If a regular window remains unavailable, report the provider state and runtime version when available. Do not supply an API key to QuotaMew or estimate a quota from other windows.

Values are not refreshing

Symptom and likely causes: Percentages look unchanged or the last refresh is old. Background refresh is every 15 minutes while running; the provider may also report unchanged data. Countdown changes are local display updates.

Safe checks: Use Refresh Now, then check refresh/provider state. Confirm the provider is enabled, its runtime can communicate normally, and your Mac is awake. Avoid repeatedly triggering refresh.

Next action: If a refresh finishes but remains unavailable, use the previous section. If refreshing stays stuck or fails repeatedly, quit and reopen QuotaMew and report the timing plus sanitized Diagnostics.

Notifications do not appear

Symptom and likely causes: A reset reminder or completed-reset notification is absent. Notifications may be disabled, denied by macOS, suppressed by Focus, already deduplicated, or ineligible because data is stale or incomplete.

Safe checks: In Settings → Notifications, enable reset notifications and select reminder times. Check System Settings → Notifications → QuotaMew and Focus. Keep QuotaMew running with a working provider, then refresh. Luna Reserve does not generate these notifications.

Next action: Read Notifications and reset reminders. A countdown reaching zero or repeatedly refreshing is not a notification test. If an expected regular-window reminder is missing, report the selected reminder and time without exposing private quota values.

Menu-bar display is not what I expect

Symptom and likely causes: You see Used instead of Remaining, the wrong provider, a dash, or a wider item. These may follow your display preferences.

Safe checks: In Settings → General, check usage display, Menu Bar Provider, Single / Overview and the Single-mode quota. Single shows one selected quota; Overview is wider and shows regular windows together. An explicit pin stays pinned when unavailable, and a missing selected quota stays a dash.

Next action: Use Menu Bar and Settings to adjust presentation. Changing a display choice does not change account limits.

Settings seem not to apply

Symptom and likely causes: A display choice has no apparent effect, or Launch at Login awaits system approval. Quota selection applies to Single mode; the pinned provider may be disabled or missing data.

Safe checks: Confirm the relevant display mode, provider enablement and macOS approval messages. Display preferences apply without refreshing. After restarting the copy in Applications, check whether the same preferences remain.

Next action: If preferences do not persist, report the category and steps to reproduce. Do not reset or delete arbitrary preference files. Launch at Login approval belongs in System Settings → General → Login Items.

Claude does not work

Symptom and likely cause: Claude is not configured or unavailable even though Claude Code is installed. Support is Experimental / Unverified; Stable's snapshot reader is not an installed bridge.

Safe checks: Read the Claude limitations. Enabling the provider does not create a compatible snapshot.

Next action: Treat Claude as unverified. Do not replace a status-line command, scan transcripts, or provide credentials to work around it. Disable the provider if you do not need the experimental card.

Something looks wrong after updating

Symptom and likely causes: Old UI remains, or a display preference differs. The old copy may still be running, or the selected provider/window may be unavailable.

Safe checks: Quit QuotaMew before replacing the app, launch the copy in Applications, and check its version in Diagnostics. Follow Updating; settings normally remain local across app replacement.

Next action: Recheck provider and display settings. If it persists, report the previous/new versions and reproducible steps; do not delete app data as a first response.

Still need help?

Use the QuotaMew issue tracker. Include the app/macOS versions, provider state, expected and actual behavior, and reproducible steps. The built-in Copy Diagnostics report can help after you review it.