Fetch pages, run crawls, and drive browser tasks from the terminal
Hyperbrowser gives Luumen a browser it can drive. Fetch a vendor status page as markdown, crawl a docs site, or hand a multi-step click-through to a browser-use task and poll it to completion. Reads come back right away. Starting jobs, creating sessions, and deleting profiles are previewed and held for approval first. Connected with an API key.
42 tools: 25 read, 17 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Hyperbrowser run looks like inside Luumen.
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — add extension, create hyperbrowser profile, create scrape job, create session, and more — is shown as a plan and requires approval by default, including the 6 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Hyperbrowser — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Connect in minutes. Every action scoped, approved, and audited from day one.