A small, supported pilot

Collect vendor invoices with an agent.

Give the repetitive browser work its own computer. We’re inviting founders and bookkeepers to try a focused workflow: collect invoices from a few agreed portals, check what is missing and review the files.

No card required to request access. We agree the scope and price before you start.

The Quokka Bot app: an agent called Errands answers when the Rijksmuseum is open on Sunday and what tickets cost, after the owner allowed rijksmuseum.nl for the task.
The current app, shown doing a browser research task. Your pilot starts with a workflow we test together.
The agent's own browser, seen live: the museum's page with the prices it read.
Its computer, live

How a task goes

  1. You ask.

    Choose the month and a few vendor portals. Agree which invoices should be there and what the finished folder should contain.

  2. It works on its own computer.

    Chrome, a workspace and Claude Code run in isolated sandboxes. Allow the sites it needs and handle any sign-in checks.

  3. You review the result.

    Check the collected files and the list of missing documents. The pilot collects documents; you keep control of accounting decisions, submissions and payments.

The safety rules sit outside the model.

Separate sandboxes, site permissions and protected login fills limit what an agent can reach. They do not replace reviewing sensitive work.

01

Its own computer

Each agent gets isolated sandboxes for its browser, its shell and its CLI. Nothing runs on your Mac or phone.

The agent's own Chrome, seen live from the app, on the museum's gallery page.

02

Only sites you allow

All traffic goes through a proxy that blocks everything by default. The agent asks before it reaches a new site; you allow it for one task or for good.

A card in the chat: the agent asks to reach notebookcheck.net and theverge.com, with Allow for this task, Always allow and Refuse.

03

A vault the model can't read

Passwords and 2FA secrets are stored encrypted. Quokka Bot types them into the page; the model never sees them.

A sign-in card in the chat with a secure form for a username, a password and an authenticator code.

04

Takeover

For a captcha, a text-message code or a card payment, take over the browser from the app, then hand it back.

The computer page while the owner has control: Hand back, and the Stop everything button.

05

Audit log and kill switch

Every action goes into a hash-chained log you can verify. One button stops the computer and cuts its network.

The activity log: the chain head hash with Verify chain, then entries for a takeover and for sites the owner allowed.

Use it from your Mac, your phone or a browser.

Mac app

Signed and notarized, for Apple silicon.

iPhone app Coming soon

Answer cards and take over from your phone.

Web app

The same app in any browser.

Start with one useful job.

Tell us what you collect each month. We’ll check whether the pilot fits.