Illustrative replay of the included local fixture. Not a live browser connection.
OBSERVE · ACT · VERIFY
A standard protocol. Your preferred agent.
CodexClaude CodeCursor{ MCP }
Local stdio configuration
LESS CEREMONY. MORE CONTROL.
One loop. Nothing hand-wavy.
Your agent stays in charge. Tablaze handles the browser mechanics and returns evidence it can use.
01 / OBSERVE
e1 textbox Destinatione2 combobox Nightse4 button Find a staysnapshot_id: …
Know what’s on the page.
Compact observations expose useful controls with references and a snapshot revision. Ask for changes instead of another full dump.
tab_snapshot
02 / ACT
fill→select→clickone ordered batch
Move through the busywork.
Keep the browser running and submit multiple actions together. If a target change is detected or a step fails, stop and report what already ran.
tab_act
03 / VERIFY
✓ URL✓ visible text✓ field value✓ element count
Check the result, explicitly.
A successful click is only a successful click. Check URLs, text, values, and visibility against the outcome you actually wanted.
tab_verify
↳Batches run in order and stop on error. They are not transactions; completed actions are not rolled back.
REAL CALLS. INSPECTABLE EVIDENCE.
Watch it work. And watch it stop.
Real SDK calls: a search batch, five outcome checks, stale-target rejection, and recovery after a fresh observation.
Normal-speed recording of actual MCP responses and tab_capture images, with labelled reading pauses. This is not a continuous video feed from the controlled tab. Uses a local fixture and no Codex or other model inference.
A local, reproducible fixture. Cold launch and warm operations measured separately. No invented competitor scorecard.
LOCAL CHROMIUM / HOTEL SEARCH FIXTUREPreparing measurement report
Cold browser + first page—median wall-clock time
Warm snapshot—median wall-clock time
Action batch—median wall-clock time
Verified runs—this fixture, this environment
Five local fixture runs, calling the browser engine directly. Excludes MCP transport, model inference, and internet websites. Run the command below from the source directory. These results are not a general reliability claim or a competitor ranking.
The core browser tools make no model API calls. Your MCP client supplies the reasoning. A Jev planner is a possible optional integration, not a shipped requirement or a feature claimed in this preview.
Can I use my existing Chrome login?
Yes, through an explicit CDP connection. The default launches an isolated browser. Attached mode shares that Chrome profile’s identity, and Tablaze closes only the tabs it owns.
What happens if the page changes?
Actions include a snapshot revision and element reference. Detected stale snapshots or changed targets are rejected; re-observe before retrying. Validation and input are not atomic, so a short race remains. These checks are not a security sandbox.
What does this preview not promise?
It doesn’t promise autonomous success on every website, the fastest result among all products, or rollback of browser actions. Uploads, downloads, closed shadow roots, and complex popup workflows need additional support.