JevMade field notes / Worked recipe

Let a browser assistant choose from visible actions

This browser recipe gives Jev a list of available controls and shows why an assistant's claim of success still needs an exact check.

Original by Jeroen Erne / NexibeoBrowser use

Bookmark Keep this in your collection.

Leave a noteWhat would you try with this?

Only you can see your notes.

Listen to this guide

JevMade’s plain-English explanation

0:00 /

AI narration

Independent ElevenLabs affiliate. JevMade may earn a commission.

Credits and license

“14 · Browser agent” by Jeroen Erne / Nexibeo. Read the original source.

This expanded guide is an AI-narrated adaptation of the source’s essential explanation, examples and caveats, not a word-for-word reading. The synthetic voice does not imitate the author or imply their endorsement.

License: MIT

MIT License

Copyright (c) 2026 Jeroen Erne (https://nexibeo.com, https://completeaitraining.com)

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

Our summary

This recipe builds a browser assistant that chooses among listed page actions instead of inventing where to click. Software reads visible links, buttons, and fields, then asks Jev which action best serves the user's goal. Password and file fields are excluded from the offered controls.

The program performs the chosen action using the control's recorded identifier and checks whether the page changed. Separate questions estimate whether the goal is complete or the assistant is stuck. Another text-generating model writes field values when typing is needed; Jev does not generate that text.

In one reported test, both the action choice and completion check accepted the wrong, similar-looking page. An exact destination check exposed the mistake. The author recommends keeping dangerous actions unavailable or behind human confirmation, and treating page content as potentially hostile instructions.

Key takeaways

Let software define which page actions are available.
Check the actual destination rather than trusting an AI success signal.
Require permission before purchases, sending, deletion, or other consequential actions.

More guides →See the experiments →