Open source Community maintained

Help, without an account.

There is no support inbox and no ticket number. Help happens in the open, on GitHub, and the guides cover most problems before you need to ask.

Read first

Troubleshooting

The install and connect guides both end with the failures people actually hit, and the fix for each.

Bug or question

Open an issue

Search the existing issues first, then describe what you expected, what happened, and how to reproduce it.

Private

Report a vulnerability

Use GitHub's private advisory form. Do not open a public issue for a security problem.

A report that gets fixed

Four things to include.

Browser agents fail in ways that are hard to guess. These four details turn "it does not work" into something reproducible.

The browser and version: Chrome, Edge or Brave, and the number from chrome://version.
What you asked for, word for word, and which mode: Chat, Fast, Research or Tasks.
What happened instead, including the last step shown in the side panel.
Any error text from the panel console. Right-click the panel, Inspect, Console.

Remove API keys, cookies and personal data before pasting. A screenshot of the panel is usually more useful than a paragraph.

Copy this into the issue

Browser:      Chrome 141.0.7390.55 (macOS)
Mode:         Fast (ultrafast)
Goal:         "search one-way ZRH to LHR on 20 Sep"
Expected:     results page
Happened:     stopped on step 4, "field rejected the value"
Console:      TypeError: ... (paste the first line)
Repro:        always / sometimes / once

Never paste a key. If you think a key leaked, revoke it with your provider first.

What support is not

HailBrowser is MIT licensed and maintained by contributors. There is no paid plan, no uptime promise and no guaranteed reply time. Issues are answered when someone who knows the area has time.

What we cannot fix

Provider keys, quotas and billing belong to Anthropic, OpenAI, Google or whoever you chose. Sites that block automation, and chrome:// pages, are blocked by Chrome itself.