Developer debug page
Find build, storage, and session details to include in a bug report.
The Developer page collects technical details about the app running on your device into one block you can copy and paste into a bug report. You never need it for everyday use — it's there so that when something looks wrong, you can hand support exactly the information they need to diagnose it.
Open the Developer page
- Open Settings → Developer (under the Account group).
- The page shows a single block of debug values.
- Click Copy in the top-right to copy the whole block to your clipboard, then paste it into your bug report or support message.
Click the refresh button next to Copy to re-read the live values (for example, current memory and storage usage) before copying.
What's in the block
- Version — the build of the web app you're running (build ID and git commit), so support knows exactly which release you're on.
- Storage — whether your messages are cached on this device persistently or only kept in memory for this visit, when that local cache was first created, and how much storage it's using. A database created hours or days ago means your cache survived between visits; one created just now means it was rebuilt. It also shows whether this is the primary tab — when you have the app open in several tabs, one tab owns the local database and the others share it, so this tells you which one you're looking at.
- Memory — how much memory the app is currently using.
- Sync — whether the live connection that keeps your messages up to date is connected and caught up.
- Identity — your user, workspace, and tenant identifiers (no passwords or secrets).
- Environment — whether you're online, on the desktop app, installed as an app, your browser, language, time zone, and screen details.
Good to know
- Nothing here changes your account or data — the page only reads values.
- The block contains identifiers and device details but no passwords, tokens, or message contents. It's safe to share with support.