For the complete documentation index, see llms.txt. This page is also available as Markdown.

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.

Last updated