Your AI Can Write the Sales Email. Can You Trust It to Click Send?

Wayne Ma — Mon, 31 Aug 2026 18:20:40 +0000

Ask AI to write a sales email and it can finish before you take a sip of coffee.

Ask it to open the right account, update the CRM, attach the right file, change a status, click Save, and confirm the change—and the babysitting begins.

Every browser click becomes a tiny trust exercise.

Is this the right customer? Is the page still current? Did the button move after a rerender? Did Save actually work? If the connection dropped after the click, will the Agent do it twice?

This is the browser gap. AI is already good at talking about work. Finishing work inside real browser tabs is harder.

The work nobody wants to supervise

Sales and operations teams live in CRMs, partner portals, support tools, recruiting systems, product dashboards, and old admin pages.

The repetitive work sounds easy:

research a prospect and update the account;
move a lead to the right stage;
prepare outreach, then record what happened;
upload an asset and check the required options;
work through a long form without losing progress.

These jobs are tedious for people and surprisingly risky for Agents. Two records can look almost identical. A modern form can replace a control while keeping it visually unchanged. An old portal may mix rich text, iframes, uploads, dynamic choices, and a separate Save button.

The worst failure is uncertainty. An action may have happened just before a timeout. Retrying could create a duplicate message, upload, or submission. Refusing to retry means the person has to inspect the page anyway.

That is why we built Saccade.

Give the Agent a tab it can be responsible for

Saccade is a live browser Truth and verified-action layer for AI Agents working in authorized Chrome and Edge tabs.

An Agent knows exactly which tab it owns. It can ask for the current semantic page or only the changes since its last read. When it acts, it uses a current page object—a field, button, choice, table, upload control, or rich-text editor—instead of guessing from an old page description.

The result comes back with a receipt. Saccade reports whether the action was accepted and whether the expected page change was observed.

If the object was replaced, the old authority stays stale. If an action may have happened but cannot be verified, the outcome stays unknown and Saccade does not quietly replay it.

In practical terms, the Agent gets clear answers to four questions:

Which tab am I working in?
Is this still the object I meant to use?
Did the action take effect?
Is it safe to try again?

That is what starts to turn browser automation from a demo into work you can hand off.

Use it where the browser is actually the best route

Saccade is the browser layer underneath an Agent, not a replacement for every API and integration.

If a purpose-built API can complete a job faster and more reliably, use it. Saccade is for the steps that genuinely live in the browser: authenticated back offices, partner sites, legacy tools, and interfaces that have no useful connector.

For sales, that may be the last mile between researched information and a correctly updated account. For operations, it may be a product listing, an upload flow, or a partner portal. For an automation builder, it means the Agent can work in the user's real session without receiving a free-form browser remote control.

We tested the part people usually wave away

The Saccade 0.2.0 release candidate went through the same blocking gates in Chrome and Edge: forms, semantic tables, iframe rich text, uploads, reconnects, replaced controls, multiple Agent sessions, and fast moving targets.

In the Mouse Accuracy gate, it completed 96 of 96 exact-target actions across the two browsers. Mean action latency in those runs ranged from 7.22 ms to 8.50 ms. The release evidence keeps those numbers attached to their test conditions.

Playwright was an important reference for strict resolution, actionability, assertions, and isolation. It remains an excellent choice for reproducible browser tests. Saccade focuses on a different job: keeping an Agent attached to the user's current, authorized browser state and returning evidence about what changed.

Try Saccade 0.2.0

The Node package is public on npm:

npx -y @nanlogic/saccade install
npx -y @nanlogic/saccade doctor

The source, Extension build, setup guide, and release evidence are public: