Browser agents

Give the job to an agent that owns it.

An agent is Browza with a job of its own — its own logins, standing instructions, the skills you've taught it, and a schedule. Set it up once; it shows up and does the work, and everything it does is on the record.

  • No credit card required
  • Free plan to start

Set up in about a minute

No pipelines, no scripts — an agent is three decisions.

01

Give it a job

Plain words. “Chase our unpaid invoices every Friday and log any replies.” That sentence is the configuration.

02

Sign it in once

Its profile keeps the logins between runs — no re-authenticating, no re-teaching every time.

03

Pick the schedule

Fridays at 8:00, or just press Run now. Both are the same run, on the same record.

An agent's morning

Watch the jobs agents own

Scripted replays of the runs a scheduled agent produces — a support queue, the books, the mentions. Pick one:

The task

▍

What happens

  1. Opens the books
  2. Reads the week's receipt pile — fourteen
  3. Enters them one by one
  4. Matches each against the bank feed
  5. One doesn't line up — $42.10, twice
  6. Flags it for you instead of guessing

Thirteen matched, one flagged

It doesn't guess with money — the odd one out is left flagged for you, receipt attached.

books.cedarledger.example/banking

Sped up and simplified for the tour — a real run streams every step live in your dashboard, and you can take over at any moment.

What an agent carries

Everything a person would keep in their head about a recurring job, kept where you can read it.

Standing instructions

Durable notes it re-reads on every run — how you like the work done, what to skip, who to flag.

Attached skills

The tasks you've taught it by doing them once yourself. An agent uses the skills it's been given — nothing else.

A schedule

Weekly, on the days you choose, at the hour you choose — daylight-saving handled, and never fired twice for the same moment.

A readable history

Every run kept: what it did, what it found, what got in the way. Nothing happens off the record.

A chat that explains

Ask what it did or what it can do, in plain words. Talking never changes its behaviour — only instructions you explicitly save do.

A beat it stays on

An agent works the sites its job needs and treats everywhere else as out of bounds — a focus boundary that keeps it on task.

Built to be trusted with a job

Three rules, designed in — because an agent you can't trust is just a liability with a login.

Status that can't lie

An agent's status is computed from what is actually happening — its runs, its login state — never stored and left to rot. It cannot claim “running” while nothing runs.

Asks first when you want it to

Set an agent to act on its own, or to stop and ask before it acts. Approval is per-agent, and a paused run waits with the browser alive — it never guesses past you.

Chat is a window, not a steering wheel

The chat answers questions about the work. It cannot quietly redefine the job — changing what an agent does takes a deliberate, saved instruction.

Agents pair naturally with persistent profiles for their logins and with skills taught through the recorder — do a task once in your own browser, and hand it to your agent forever.

Hire your first agent

Name it, give it a job, pick a schedule — the whole setup takes about a minute.