Reference
Browser support
Which browsers are supported, known limitations, and how to report issues.
Supported browsers
The platform is tested against the latest two major versions of:
- Chrome (and Chromium derivatives like Edge, Brave, Arc)
- Safari (macOS and iOS)
- Firefox
Older versions may work but aren't actively tested. If you're stuck on an older browser, parts of the UI (the command palette, streaming answers, the foresight composer) may misbehave.
Recommended
Chrome on macOS / Windows for the best experience. Most internal testing happens there, so visual fidelity and feature timing are tuned for it.
Known limitations
- iOS Safari — uploads work but are slower; the streaming reasoning view occasionally pauses on iOS background tabs (Apple's energy-saver). Foreground the tab to resume.
- Firefox — works end-to-end, but some animations (decision-sign radar, foresight chips) are lighter than in Chrome.
- Mobile sized screens — the Reasoning composer and the Ontology graph are designed for ≥ 1024px wide. Below that, you'll get a usable but compressed layout. A dedicated mobile experience is on the roadmap.
- Print — printing a reasoning answer or a decision detail page works (Cmd/Ctrl + P) but is unstyled. For shareable output, use Reports instead — they have a clean export path.
Browser features required
- JavaScript — required (the platform is a JS app).
- Cookies — required (session cookie + workspace/project context cookies).
- WebSocket / EventSource — required (the streaming reasoning answer uses Server-Sent Events).
- Local storage — used for non-critical UI preferences. Disabling it doesn't break the app.
Browser extensions that occasionally cause issues
- Grammarly / LanguageTool — inject DOM attributes that sometimes flag a hydration warning in the console. The app handles this; it doesn't affect functionality.
- Ad blockers / privacy extensions — should be fine for the app domain. If they're set to block all third-party requests, sign-in via Google OAuth may break. Allowlist your platform domain.
- Translate plugins — translating the page mid-session can break interactive elements. Leave translation off on the platform.
Reporting a browser-specific issue
If something works in Chrome but not in another browser, that's a bug worth reporting. Include:
- Browser name and version (e.g. "Safari 18.0.1 on macOS 15.1")
- The exact URL where the bug shows up
- A screenshot or video
- Console errors (DevTools → Console)
Send to your operator's support channel.