Skip to content

Live tools

Live tools: the agent writes a tool for one site, and you keep it

When no built-in tool does the job, the agent writes one in JavaScript for that page. You read the code before it runs, and a tool you keep runs by name, without the agent.

Steps

How a live tool is made

  1. 01

    Ask for what no tool does

    Turn on the Live tool switch and describe the job: seek a video, read a canvas, archive every row.

  2. 02

    Read the code

    The panel shows the full source, never truncated, and you approve that source before it runs.

  3. 03

    Keep it

    A second after it works, the panel asks whether to keep it. Name it, or take the name it suggests.

  4. 04

    Run it by name

    Type / on that site and pick it. It runs without the agent and without asking you again.

The name

How a live tool is named

The name has three parts: the site, the kind of page, and a name you choose. Only the last part is yours.

/youtube.com:watch:darken-page-except-video-player

The site

Where it was made, and the only place it runs.

The kind of page

The first part of the path. Every watch page, not one video.

What you called it

Yours to name. This is the part you type.

Scope

Where a live tool is offered

On pages of the same kind, on the same host. A tool made on a YouTube watch page is offered on every watch page and nowhere else.

  • youtube.com/watch?v=anything offered
  • youtube.com/watch/live offered
  • youtube.com/results not here
  • youtube.com not here
  • music.youtube.com/watch not here

Examples

Small fixes for pages you use often

Each is a few lines the agent writes once.

darken-page-except-video-player

The dark mode the site never shipped, on the one page you watch.

collapse-bot-comments

Fold every automated comment on a pull request so the human ones are left.

archive-newsletters

Clear the promotions out of an inbox in one press instead of forty.

copy-table-as-csv

Take the table a dashboard will not export and put it on the clipboard.

Security

Where a live tool is stored, and what can call it

The code stays in the browser

The extension stores it. Browsentic Bridge learns that a tool exists and what it does, never its code.

Nothing runs unread

You read the source before its first run. Keeping the tool is what lets later runs skip the prompt.

MCP clients cannot reach it

It is not a page tool, so nothing an MCP client can call touches it. Only the side panel can run it.

Removing one

Type /remove-tools for the list, with a cross beside each. Removing a tool deletes its code.

Give your browser a superpower.

Free and open source under Apache 2.0, with no API key, subscription or account. One line installs Browsentic Bridge and opens the extension’s store page. Nothing connects until you pair the two.