Nanobrowser alternative

Half of the job you are behind on is not on a web page.

Think about the pile you have been walking past since Monday.

Say it was the two hundred applications sitting in the hiring inbox, for your hiring manager. The CVs are PDF attachments. The scoring sheet is a spreadsheet. The thing that actually decides each one is a profile page you have to open and read.

Nanobrowser's README describes an open-source web automation tool that runs in your browser. Its own worked examples are web tasks, such as extracting the top ten headlines from a news site.

The applications are not a web task. They are one job made of three kinds of material, and only one of them is a page. Strawberry takes all three. Your AI companion opens the attachments, reads the profile pages you are already signed into, and fills the scoring sheet with a link beside every score.

Your AI companion reads the attachments, not only the pages.

A CV is a PDF and it is never going to be anything else.

Your AI companion opens PDF files up to 50 MiB and reads them page range by page range until it has what the job needs.

Documents work the same way. It can create, inspect and revise a Word file, and it writes the result to a new file so the original stays exactly as it was. Spreadsheets are handled as spreadsheets rather than as text pasted into a chat.

Everything it produces lands in a workspace you own. Search finds a phrase inside a nested file, not only in the file names. Every synced file keeps version history showing when it changed and why. Anything deleted stays recoverable for thirty days.

The shortlist has to arrive somewhere your hiring manager can act on it.

A scored list you still have to copy somewhere is half a job.

The shortlist arrives as rows in the hiring sheet with a link beside each score. The four people worth interviewing become calendar invitations. The rejection notes sit in your drafts, unsent, until you have read them. That is what 2,000+ integrations are for, and the destination matters more than the number.

Getting the scores right takes the reading. Strawberry is not something you add to a browser. It is the browser itself, on Mac and Windows. Your AI companion opens the profile page, the portfolio site and the applicant tracking system inside the sessions you already have.

Nanobrowser's README lists Chrome and Edge as officially supported, and lists Firefox, Safari and other Chromium variants as not supported.

Nothing reaches a candidate until you have seen exactly what it says.

Reading an application, writing a rejection, sending that rejection and changing a live record carry four different risks. Strawberry treats them as four separate decisions, and you make them before any work starts.

Every connected action is set to ask, always allow, or off. Let it draft every rejection. Require your approval before a single one sends. Switch anything you do not want touched off completely.

When approval is needed you get an editor rather than a yes or no box. You see the recipient, the full text, the attachments and the destination before it moves. On a reply it shows you the address it resolved, so you can correct it, and it never quietly copies the rest of the thread back in.

The person who runs hiring next should inherit the AI companion, not the prompt that worked once.

The role opens again in March, and somebody else runs it.

Save the job once and Strawberry keeps how you like it done. Which signals count, which ones you have decided not to trust, and the point where you want to look before it carries on.

Then give it a schedule, or a trigger such as a new application arriving by email. Every run records what it did and what it cost, including the runs that failed, so a month of unattended work is auditable rather than assumed.

Nanobrowser's README documents conversation history you can access and manage.

What Strawberry hands over is a colleague. An AI companion carries its memory, its skills and its configuration, so the person hiring in March receives someone who already read two hundred applications with you. The applicant tracker still asks them to sign in, exactly as it asks you. Your team workspace holds the shared files and the scoring standard, and shared credits cover whoever needs them.

Frequently asked questions