# In Plain English Think of a website as having two layers: the front-of-house that humans see, and the request layer the browser quietly uses underneath. Traditional automation stays stuck in the front-of-house, clicking through the human interface. Unbrowse learns the request layer and reuses it, the way a regular at a restaurant skips the menu and orders the dish by name. Nothing about your permissions changes; the assistant still only does what you could already do yourself. This is usually faster and more reliable because the human interface is the brittle part: it changes layout, shows popups, and slows down, while the underlying request is comparatively stable. Reusing the stable layer means fewer surprises and far less waiting. A few things Unbrowse is not, to avoid a common misread: * It is not a permission bypass. It cannot reach anything you could not already reach yourself. * It does not publish your credentials. Sign-in stays on your machine. * It does not replace the browser everywhere. It uses one whenever a site genuinely needs it. If you want the operating model an AI agent actually follows, continue to For Agents. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.unbrowse.ai/start-here/in-plain-english.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.