Troubleshooting

Start with the symptom that matches. Most extension issues are “app not running” or “wrong page.” In the app, Settings → About links back here and to feedback.

Usage not updating

  • Click Refresh on the dashboard.
  • Confirm the provider still shows as connected (not Disabled) in Settings → Providers.
  • Re-test the connection; sessions expire and may need a reconnect via the extension or Reauthenticate.
  • Provider APIs change — if one provider fails while others work, wait for an app update or try reconnecting.
  • Offline? Vale skips scheduled fetches, keeps the last known usage on each card, and sends one alert for the outage. Refresh resumes on its own once the network is back.
  • Timeouts and dropped connections get one quick retry; a request that stays stalled fails fast with a clear message instead of hanging the refresh.

Undocumented API breaks

  • Most providers (except OpenRouter’s credits API) use undocumented endpoints. Sites can change without notice.
  • If refresh fails with auth or parse errors after a provider redesign, reconnect or wait for a Vale update.
  • Check Settings → About for per-provider Stable vs Undocumented badges, Check for updates, and the Changelog.
  • Report a break via feedback (include Vale version from About, provider, and the error you saw).

Sign-in and connection sync

  • Email sign-in is required — there is no local-only guest mode.
  • No code? Check spam, use Resend code or Open email app on the OTP screen, or open the magic link from the same email. Codes are exactly 6 digits; copying them from the email's digit boxes and pasting works.
  • Sign out on a slow or broken network still signs you out locally — the stored session is dropped even when the server cannot be reached.
  • If sync seems stuck, sign out from the sidebar account menu (or Settings → Account) and sign back in.
  • Usage history never syncs — only provider connection metadata does.
  • Antigravity OAuth: complete the Google flow in-app; do not expect the browser extension to connect it.

Kimi session ended

  • Kimi moved from kimi.com to kimi.ai. Web sessions last about 15 minutes and Vale renews them; if renewal fails you will see “Kimi session ended”.
  • Fix it with Sign in with Kimi on the Reauthenticate prompt — Vale gets its own session that renews without touching your browser.
  • Or sign in at kimi.ai again and reconnect through the extension (it hands the session to Vale and keeps kimi.ai signed in).
  • “Duplicate account” on Sign in with Kimi means that Kimi user is already connected — edit the existing connection instead.

Billing and subscription

  • After starting a trial or checkout, open Settings → Billing and use Refresh status if Power features stay locked.
  • Update payment method, view invoices, or cancel from Settings → Billing — actions route to Stripe or Paymob based on how you subscribed.
  • Payment Provider preference (Auto / Stripe / Paymob) affects the next paid checkout; it does not move an existing subscription between processors.
  • Payment failed? Paid Power stays active for a 7-day grace period while the charge is retried, and you get an email with the next retry date. Update your payment method in Settings → Billing to avoid interruption; trials have no grace period and end at the trial end.
  • Lifetime complimentary grants show as Power without update-payment / cancel actions — use feedback or email support if status looks wrong.
  • See Billing for plan limits.

Free account limit

  • Free allows up to five active accounts (provider connections). Two Cursor accounts count as two. Disable or remove one in Settings → Providers to add another, or upgrade to Power.
  • Hitting the limit explains it in plain words and shows the upgrade dialog in place — you stay on the Providers page. Re-saving an existing connection never counts as a new one.
  • After a Power plan ends, Vale may keep extra connections but disable all except the five oldest — re-enable only within the Free cap, or subscribe again.

Extension won’t connect

  • Vale desktop must be running (it owns port 3456 on localhost).
  • Extension enabled; reload it from the browser’s extensions page after updates.
  • You must be on the matching provider URL (see Extension).
  • Sign in on the provider site first, then open the popup and Connect.
  • In Vale, start Add Provider with Browser Extension first — the extension needs Vale to be waiting.
  • Connect is offered on every page where the provider script runs, not only the usage page — but stay on the provider's own domain.
  • Zed accounts in several organizations: Vale asks which organization to monitor; pick one and the save retries.
  • Refresh the tab and try again.

Vale doesn’t receive credentials

  • Firewall or security software blocking localhost HTTP to 127.0.0.1:3456.
  • Another process using port 3456 — quit other Vale instances.
  • In Add Provider, stay on Browser Extension / waiting until Connect succeeds.

Notifications

  • Allow notifications for Vale in system settings.
  • Confirm Enable notifications is on in Settings → Notifications.
  • Custom quota/credit thresholds and Notify on limit reset require Power.
  • Too many alerts? Vale sends one per outage and only reports a reset when a window actually refills; an alert that repeats on every refresh is a bug — report it with the provider and metric.

Android app

  • No providers on the phone? Providers are added on desktop. Open Vale on your computer, sign in with the same email, add the provider, then pull down on the phone dashboard to refresh.
  • No alerts? Allow notifications when asked (Settings → Notifications shows “Push notifications · Allowed”), and set Auto-refresh to a period other than Manual so background monitoring runs.
  • Alerts arrive late while the phone is idle? Android's battery saving limits background wake-ups to roughly every 9 minutes, and less often the longer the screen stays off. Checks catch up as soon as you use the phone.
  • The “Monitoring” notification is the background service. Its Stop action sets refresh to Manual; hide it from the channel settings if you prefer silence.
  • An account expired on the phone? Kimi and Antigravity tokens renew on the phone itself; other expired sessions are fixed with Reauthenticate on desktop.

Still stuck?

Use the feedback form (also linked from Settings → About → Feedback) — include your Vale version, provider, and what you saw. Or email support@valeapp.app. The product repo is private — there is no public GitHub issues tracker.