Why DocuBench Browser?
DocuBench Browser uses Chromium, the same open-source browser engine that powers Google Chrome, Microsoft Edge, and Brave. A natural question is:
why not just use the browser I already have?
This is a fair question, and we want to give you an honest answer.
Your Browser Is Your AI's Eyes and Hands
The DocuBench Browser is not just a place to view web pages — it is a direct extension of your AI workbench.
Read any page, instantly.
Open a web page in DocuBench Browser and your AI can read its full content immediately. No copy-pasting, no manual uploads. Reference a report, a dashboard, a news article, or a product page — and the AI has it.
See what you see.
Your AI can take a screenshot of any tab, including content that requires scrolling. If a chart, diagram, or a layout matters, the AI sees it visually, not just as text.
Tabs as resources.
Each browser tab you open becomes a named resource your AI can reference. You can say "summarize [2]" or "compare the content in [1] and [3]" and the AI knows exactly what you mean.
Work quietly in the background.
DocuBench can silently load a URL, capture its content, and pass it to the AI — without interrupting the tabs you are working in. Background research happens without disrupting your flow.
Take action, not just read.
DocuBench Browser can interact with pages on your behalf. For example, when the AI drafts a Slack message for you, it can place the text directly into the Slack composer — ready for your review and send.
Beyond a Chat Box
We are continuously exploring deeper integration between the browser and AI, so that more of your workflow happens naturally, without you having to orchestrate every step.
These capabilities require deep, direct access to the browser. They go far beyond what any browser extension can offer.
Why Not Just Connect to Chrome?
We hear this request. Re-logging into sites you are already signed into in Chrome is friction, and we take that seriously. We explored several ways to connect to Chrome directly. Here is what we found — and why we decided against it.
It would put your security at risk.
The most capable way to connect to Chrome programmatically is through its remote debugging protocol. When enabled, this channel gives an app deep control over Chrome — reading tabs, accessing cookies, and interacting with page content. Because it binds to a local port with no authentication, other processes on your computer can connect to it too. This is a real and documented attack vector.
Your sessions might not transfer anyway.
Some sites — particularly Google, Microsoft, and financial services — actively detect when a session is being used in an unusual context and may prompt re-authentication. Whether cookie import would work reliably varies by site and circumstance. The feature could not deliver a consistent experience.
Chrome extensions can't do what our AI needs.
A Chrome extension can read the page you are currently viewing. But it cannot take full-page screenshots, load pages silently in the background, or interact with page elements the way DocuBench needs to. Building Chrome integration through an extension would mean losing the AI capabilities that make DocuBench useful — a trade-off that helps no one.
Sharing browser data carries real risk.
Another option we considered was reading Chrome's saved session data directly from your system. This requires accessing your system's secure credential storage — the same place your passwords are kept. Even with your explicit permission, we felt this was too sensitive an operation to build into a routine workflow.
A Browser Built for Trust
Rather than compromise on security or capability, we built a browser designed from the ground up for the DocuBench workflow.
Your browsing is isolated.
The DocuBench Browser runs in a fully sandboxed environment, completely separated from your other applications. Web pages in DocuBench cannot access your files, your other apps, or anything outside the browser window.
Your session belongs only to you.
Each DocuBench account gets its own private session — completely separate from any other user and from the rest of your system. Cookies, saved logins, and browsing history stay inside your DocuBench session and go nowhere else.
Web pages cannot reach your AI data.
The web pages you browse have no way to access your conversations, your files, or your AI results. The wall between the web content and your workspace is enforced at the system level, not just by policy.
No tracking, no profiling.
We do not analyze your browsing behavior or share what sites you visit. Your browsing history inside DocuBench exists solely to power your workflow.
We Welcome Your Feedback
We know that signing into sites again inside DocuBench is the most common point of friction. We are actively working on ways to reduce that friction without compromising the security practices.
If you have questions or feedback about the browser experience, we would love to hear from you at support@docubench.ai.