---
title: Browser & Cache
description: 'Resolve cache, extension, and browser compatibility issues on the platform.'
tags:
  - troubleshooting
  - browser
---

## Minimum browser requirements

The platform requires a modern browser with JavaScript ES2022 support, WebGL 2.0, and IndexedDB.

| Browser | Minimum version | Status |
|---------|----------------|--------|
| Chrome | 90+ | Fully supported |
| Firefox | 88+ | Fully supported |
| Safari | 15+ | Supported (minor 3D viewer differences) |
| Edge | 90+ | Fully supported (Chromium-based) |
| Brave | Latest | Supported with shields adjustment (see below) |
| Opera | 76+ | Supported |

**Unsupported browsers:**
- Internet Explorer (any version)
- Safari 14 and earlier
- Chrome on Android below version 90
- Samsung Internet below version 15

**How to check your version:**
- Chrome: Navigate to `chrome://version`
- Firefox: Navigate to `about:support`
- Safari: Safari menu then About Safari
- Edge: Navigate to `edge://version`

## Quick fixes

Before investigating further, try these steps in order:

1. **Hard refresh.** Press `Ctrl+Shift+R` (Windows/Linux) or `Cmd+Shift+R` (macOS) to bypass the cache and reload all assets.
2. **Incognito window.** Open the platform in a private/incognito window. If the issue disappears, an extension or cached data is the cause.
3. **Clear site data.** In your browser settings, clear cookies and cached files specifically for `*.ivybiosciences.com`.
4. **Different browser.** Try a different browser entirely to isolate whether the issue is browser-specific.

## WebGL 2.0 requirements

The platform's 3D molecular viewers (Mol*, NGL, 3DMol) require WebGL 2.0 for hardware-accelerated rendering.

**Checking WebGL 2.0 support:**
- Chrome: Navigate to `chrome://gpu` and look for "WebGL2" in the Graphics Feature Status section. It should say "Hardware accelerated."
- Firefox: Navigate to `about:support` and search for "WebGL 2" in the Graphics section.
- Safari: WebGL 2.0 is supported in Safari 15+. There is no built-in diagnostic page; visit `webglreport.com` to test.

**Common WebGL issues:**

- **"WebGL is not supported" error.** Your browser or GPU does not support WebGL 2.0, or it has been disabled. Check if hardware acceleration is enabled in your browser settings.
- **Black or blank 3D viewer.** The WebGL context was created but rendering failed. This often indicates outdated GPU drivers. Update your graphics drivers from the manufacturer (NVIDIA, AMD, Intel).
- **"Too many WebGL contexts" warning.** Browsers limit WebGL contexts to 8-16 per page. If you have many 3D viewer cards open on the canvas, close some to free contexts.
- **Slow or choppy 3D rendering.** Integrated GPUs (Intel UHD, Apple M-series integrated) work but are slower for large structures. Reduce the representation detail or close other GPU-intensive tabs.

**Forcing software rendering (fallback):**
- Chrome: Launch with `--use-gl=swiftshader` to force software rendering. This is much slower but works without GPU support.
- This is a last resort for machines with broken GPU drivers. Performance will be significantly reduced.

## IndexedDB requirements

The platform uses IndexedDB for local session persistence, including the agent runtime's checkpoints.

**If IndexedDB is unavailable:**
- Chat session recovery after a browser crash won't be available.
- Some large result sets may load more slowly because they can't be cached locally.

**Common IndexedDB issues:**

- **"QuotaExceededError" in the console.** Your browser's storage limit for the site has been reached. Clear site data or increase the storage limit. Chrome allows sites to use up to 60% of total disk space by default.
- **IndexedDB in incognito.** Private windows keep IndexedDB in memory only, so anything stored there is gone when the window closes. Session recovery won't survive closing a private window.
- **Local data missing after clearing site data.** Clearing site data deletes the IndexedDB databases. This is expected, and the platform rebuilds them from the server in your next session.

## Extension conflicts

Browser extensions can interfere with the platform's functionality. Here are the most common conflicts.

### Ad blockers (uBlock Origin, AdBlock Plus, Ghostery)

Ad blockers may block:
- API requests to the platform's backend (mistaken for tracking requests).
- Font and icon loading (blocked CDN domains).
- WebSocket/SSE connections (blocked as potential data exfiltration).

**Fix:** Add `*.ivybiosciences.com` to your ad blocker's allowlist. In uBlock Origin: click the extension icon, then click the power button to disable for this site, then reload.

### Privacy extensions (Privacy Badger, DuckDuckGo Privacy Essentials)

Privacy extensions may:
- Block third-party cookies required for Clerk authentication.
- Strip headers from API requests, causing `401` errors.
- Block connections to Clerk's authentication domain.

**Fix:** Allowlist both `ivybiosciences.com` and `clerk.ivybiosciences.com` in the extension's settings.

### Dark Reader and theme extensions

Dark Reader and similar extensions that inject CSS can:
- Break the layout of scientific visualizations and charts.
- Invert colors in molecular viewers, making them unreadable.
- Interfere with canvas card rendering.

**Fix:** Disable Dark Reader for `ivybiosciences.com`. In Dark Reader: click the extension icon then toggle off "ivybiosciences.com" in the site list.

### Password managers (1Password, LastPass, Bitwarden)

Password managers may:
- Autofill form fields that are not login forms (SMILES input, parameter fields).
- Overlay their UI on top of input fields, blocking interaction.

**Fix:** If you see unexpected autofill in non-login forms, disable the password manager's autofill for `ivybiosciences.com` or use the extension's site exclusion list.

## Brave browser shields

Brave's built-in shields are aggressive by default and may block features the platform needs.

**Recommended Brave settings for the platform:**
1. Navigate to `ivybiosciences.com`.
2. Click the Brave shields icon (lion) in the address bar.
3. Set "Trackers & ads blocking" to "Disabled" for this site.
4. Ensure "Block fingerprinting" is set to "Allow fingerprinting" for this site (required for WebGL).
5. Ensure "Block cookies" is set to "Only block cross-site cookies" (not "Block all cookies").

## Mobile browser limitations

The platform is designed primarily for desktop browsers. Mobile browsers have specific limitations.

**What works on mobile:**
- Browsing shared results via public links.
- Reading documentation.
- Viewing job status and basic results.
- Chat conversations (text only, no 3D viewers).

**What does not work well on mobile:**
- Canvas interactions (cards require hover/drag, which is difficult on touch screens).
- 3D molecular viewers (limited WebGL performance, small screen).
- File uploads (mobile file pickers are limited).
- Multi-tool workflows that produce many simultaneous results.

**Recommended:** Use a desktop or laptop browser for active research work. Mobile is best for monitoring job status and reviewing text-based results.

## Incognito and private mode

Incognito/private mode is useful for diagnosing issues but has specific limitations.

**Differences in incognito:**
- No extensions are loaded (unless individually enabled for incognito).
- No cached data from previous sessions.
- Cookies are cleared when the window closes.
- IndexedDB data is kept in memory only and discarded when the window closes.

**When to use incognito for diagnosis:**
- To confirm that an issue is caused by an extension (if the issue disappears in incognito, an extension is the cause).
- To test with a fresh session (no stale tokens or cached data).
- To sign in with a different account without signing out of your main session.

## DevTools checks

If the above steps do not resolve your issue, use the browser DevTools (F12) to gather diagnostic information.

**Console tab:**
- Look for red error messages. Common ones include CSP (Content Security Policy) violations, failed network requests, and JavaScript errors.
- Filter by "Error" level to hide informational messages.

**Network tab:**
- Reload the page with the Network tab open.
- Look for requests with status codes 401, 403, 429, or 5xx.
- Blocked requests appear with a status of `(blocked)` and indicate extension or firewall interference.

**Application tab:**
- Check "Local Storage" and "IndexedDB" for `ivybiosciences.com`. If storage is full or corrupt, clearing it may resolve UI issues.
- Check "Service Workers". The platform registers one at `/sw.js` for tab coordination, notifications and online/offline status. It doesn't cache pages or API responses, so a stale-page problem isn't coming from it. If some other service worker is registered for the site, unregister it and reload.

## Ticket checklist

If you need to contact support about a browser issue:

- Browser name and exact version number
- Operating system and version
- Whether the issue occurs in incognito with all extensions disabled
- Screenshots of the Console and Network tabs showing errors (omit sensitive data)
- Whether the issue occurs on a different computer or browser