Help
Something went wrong, or the app won't load? You're in the right place.
WaxFrame · loading version…
Start with what you were trying to do
Most WaxFrame problems fit one of these plain-English situations. Pick the closest one first; the technical tools below are only there if support needs more detail.
Try a hard refresh first: Ctrl+Shift+R on Windows/Linux or ⌘+Shift+R on Mac. WaxFrame is desktop-only, so make sure your browser window is at least 1366×768.
That usually means the provider rejected the key, billing is not enabled, or the provider is temporarily refusing requests. Open the API Key Guide and check the provider-specific steps before changing your document setup.
That is fixable. Add a direct instruction in Notes, edit the Project fields if the goal was vague, or restore an earlier round from Round History. The User Manual explains those choices without requiring technical background.
📋 Support info
If you need to report a bug, this is gathered automatically — no personal data, no document text. Copy it into your bug report so support knows what you're running.
Gathering…
Report a bug
Two quick steps. Your API keys and license are always stripped from anything this page produces.
Opens a new GitHub issue with your environment already filled in. Add what happened and the steps to reproduce it.
For intermittent failures (rounds that fail sometimes but not always) or hard-to-reproduce bugs, turn on Deep Dive capture in WaxFrame before reproducing the issue. It records per-API-call telemetry — request/response shapes, finishReason, payload sizes, token counts, timing — into a ring buffer of the last 200 calls. The diagnostic bundle (Step 3) picks that up automatically. Off by default; you can turn it back off from Settings → Diagnostics when you're done.
Click below to flip it on now. Then open (or refresh) WaxFrame in another tab, reproduce the issue, and come back here for Step 3.
A support-safe snapshot of your setup and session. Download it, then drag the file into your GitHub issue.
Found a security issue instead? Please don't post it publicly — use GitHub's private vulnerability reporting on the Security tab.
Advanced support tool: compare provider models
Use this only when support asks you to compare WaxFrame's saved model list against a fresh provider fetch. The live fetch does not write to your cache.
Pick a provider, then dump models.
Live fetch waits until you click Dump models.
🔧 Try these first
Most issues clear with one of these.
- Hard refresh. Ctrl+Shift+R (Windows/Linux) or ⌘+Shift+R (Mac). Clears a stale cached file after an update.
- Check your window size. WaxFrame is desktop-only and needs at least 1366×768. A narrow or zoomed window triggers the minimum-size overlay.
- Try another browser. A recent Chrome, Edge, or Firefox. Private/incognito windows can block the storage WaxFrame needs.
- Last resort — reset local data. If the app is stuck in a bad state, see the Advanced reset section below for a one-click reset.
Advanced reset: wipe local data
Use this only when you are uninstalling, starting completely over, or support tells you the app is stuck because old saved browser data is in the way.
WaxFrame stores everything locally in your browser across three storage layers. Nothing leaves your machine. The buttons below are stacked in storage-layer order — the first three each wipe one layer, and the last wipes everything. After any wipe the page reloads so the app starts fresh.
What each layer holds:
- localStorage — your AI list, API keys, custom-AI configs, project fields, license, Auto-mode settings, recommendation caches, model caches, UI prefs (collapsed/expanded rows, etc.).
- IndexedDB — your session data: round history, working document text, console history, conflict ledger snapshots. This is where the document and rounds you can see right now actually live (localStorage has a 5MB cap, IndexedDB is much larger).
- sessionStorage — per-tab storage the browser clears automatically when you close the tab. WaxFrame doesn't currently use it — this button is here as a thorough cleanup in case a future feature does.
What this does NOT touch: any data on the AI provider's servers (your API account, your keys, your usage history). To revoke an API key, do that in the provider's console (API Key Guide).
Wipes are irreversible from inside the app. If you have a hive or project worth keeping, save a checkpoint first (Menu → 💾 Checkpoint - Save) before wiping.