Screens

Everything below is the real extension in a real browser. Nothing is mocked, staged or cropped to hide a step. The three panels are the surfaces you interact with; the run afterwards is what one of them looks like with a task in flight.

The panel

The Brotto panel idle, with suggestions — **Idle.** The panel offers what the page in front of you could be asked to do.

The session history list — **History.** Every run, on your own disk, yours to delete.

Brotto's settings: bring your own model key, and the sites it refuses — **Yours.** Your model key, your server, and the list of sites Brotto refuses outright.

One run, start to finish

One task, four moments: Brotto adding a branch protection ruleset to its own public repository. Note where it stops — not once at the end, twice mid-run, because both were decisions only you could make.

You ask for it in a sentence

There is no form and no workflow to learn. The panel is a chat box, and whatever you can describe is the whole interface.

Brotto's panel with the task typed out: go to GitHub, find the Brotto repository, add a branch protection ruleset to main, and open a pull request for it

It asks before it leaves

GitHub is the first domain this run touches, so it stops and waits. A domain you approve is remembered for good — consent is for the site, not for the one verb — and a page Brotto has never seen cannot be pre-approved by anything but you.

Brotto's panel showing a first-navigation approval card for github.com, with Allow and Deny buttons

It stops again when the page offers a choice

GitHub has two ways to add branch protection, and picking wrong means clicking back through settings. Rather than guess, it hands you the question and waits. This is the same card you would get for a sign-in it cannot pass.

Brotto's panel stopping to clarify that the repository has two ways to add branch protection, with Skip and Say options

The run finishes, and the whole thing is on your disk

The panel reports what it did and what it would do next. Nothing is sent here: the ruleset was written on github.com by your own session, and the transcript lands in logs/sessions/ beside the rest of your files.

Brotto reporting DONE: it created a classic branch protection ruleset on the main branch of the Brotto repository, with targets, enforcement status, required checks and force-push settings

Twenty-five seconds

The video

What it looks like in motion

A pass through the product: the panel opening, a task being read, an approval coming back, a run finishing. It is a showcase of the shapes you will see, not a recording of one session — the session above is the real one, moment for moment.

Install it yourself — one container and one extension, about six steps. Or read the README for the same thing with the commands inline.