Kazzle supports three browser backends. Each has different strengths.Documentation Index
Fetch the complete documentation index at: https://docs.kazzle.com/llms.txt
Use this file to discover all available pages before exploring further.
Kazzle Browser (built-in)
The default. A full browser embedded in the desktop app. Per-space cookie isolation. Multiple tabs per session.- Works offline
- The AI and you share the same tabs
- No setup required
Cloud browser
Disposable cloud browser sessions for automation and scraping. Multiple parallel sessions per profile, with stealth defaults and a live view URL you can watch.- 72-hour session timeout, auto-recreated on the next tool call
- Best when you need clean sessions, parallel runs, or stealth
Chrome or Brave (extension)
Connect your real Chrome or Brave browser to Kazzle via the Chrome extension. The AI controls the same browser window you see.- Your browsing is the AI session - shared view
- One session per profile (the operating system locks the profile)
- Install from the Chrome Web Store, or load unpacked in development
Connecting
- Go to Settings > Computers in your space
- Click Connect browser
- Install the Kazzle extension if prompted
- Chrome opens with the extension active. The AI can now navigate, click, and read your browser.
Session lifecycle
A browser session represents one live browser connection. Sessions are created when you (or the AI) open a browser, and destroyed when closed.| Backend | Sessions | Lifecycle |
|---|---|---|
| Kazzle Browser | One per space | Lives as long as the tab is open |
| Cloud browser | Multiple per profile | 72h timeout, auto-recreated |
| Chrome / Brave | One per profile | Ends when the extension or browser closes |