In practice
Ordinary browsing work, in sites you are already signed in to: the negotiation, the application, the cancellation, the thing you redo every Friday. The agent senses what is in front of it, works out what the job needs and sees it through. Anything that commits something, or sends it to someone other than you, pauses first and names itself before it happens.
Worked example
Attach your resume once. Browsentic takes it in there and then and keeps notes on it, so the agent knows what it is offering without ever seeing your filesystem. From then on it senses the posting in front of it, weighs it against what you have actually done, answers the application in your own words, and hands over the file the form is asking for. Both of the steps that reach the employer stop and name themselves first.
page_listFiles
resume.pdf · read once, at attach time
page_getPageInfo
application form · 22 fields, 3 required
page_fillInput
experience · matched to your resume
page_attachFile
resume.pdf, where the form asks for it
asks you first
page_submitForm
the step that reaches the employer
asks you first
Six more
Each one names the tools it reaches for, and the moment it stops and hands the decision back to you.
Your account, your ticket history, last year’s invoice open in the next tab. It takes in what support actually said, weighs it against what you paid before, drafts the counteroffer in your own words, and holds right at the moment it would reach them.
page_extractTextpage_typeTextpage_submitForm
Pauses at Send, under the form-submission rule
Point it at a billing page and it works out where the cancellation actually lives, sees the retention offer for what it is, answers the exit survey and comes to a halt in front of the one step that cannot be undone. The consequence is the last step, so that is the step you keep for yourself.
page_getPageInfopage_clickElementpage_extractText
Name page_clickElement in requireApproval and the final step asks first
Start the upload, the build or the export, then hand the tab over. It senses the progress a page gives off, keeps percent and ETA in view from the background, and tells you the moment it lands. Nobody has to sit watching a bar that moves once a minute.
page_startMonitorpage_awaitMonitorpage_monitorStatus
Nothing to approve. It is only watching
Show it once, with the recorder on. Browsentic keeps ordered steps named after what you accomplished, and whatever you typed comes back as a placeholder it asks you for. Next Friday the whole instruction is “do it like last time”.
page_listRecordingspage_readRecordingpage_fillInput
Replay is a plan, not a script. A step that no longer lands halts the run
Five tools you are logged into, one summary. It takes each one in as rendered text, the way it appears to you, rather than scraping markup full of hidden nodes and off-screen strings that never met your eyes.
page_extractTextpage_screenshotpage_openTab
Raw HTML reads are denied by default, hidden text with them
The same twelve fields across forty rows: the job nobody schedules and everybody postpones. It works each record through, checks what came back against what it expected, and moves on, stopping the moment a page stops resembling the one before it.
page_fillInputpage_submitFormpage_waitForElement
Asks each time it commits one, until you grant Always on this host
The gate
Approval prompts appear in the side panel with the action named. Form submission is gated by default, because it is the one effect that leaves your machine and lands on somebody else's desk.
Form submission and file upload. Both reach an outside party, so both name themselves and wait.
Name a tool in requireApproval and it asks every time, which is useful for the last click of a cancellation.
Approve once with Always on this host when you are working a long list and every row asks the same question.
Free and MIT licensed. Nothing to sign up for, no key to paste, and a fresh install connects to nothing until you redeem a pairing code yourself.
claude mcp add browsentic -- browsentic-mcp