Conversations

Voice and text #

Three ways in:

Speech uses the browser's built-in recognition. Nothing is bundled or downloaded — which in Chrome means audio is streamed to Google for transcription. Type instead if that matters to you; see Limits.

Replies stream back token by token. Follow-ups continue the same conversation, so "now click the second one" works.

Words are not the only way to say which thing you mean. The composer's lens button opens A-Eye: point at an element on the page and it rides along with your next message as its subject.

One conversation per tab #

Each tab gets its own conversation, and several can run at once.

A conversation is bound to the tab it started in. It keeps working there while you read something else, and its actions stay in its own tab instead of following whichever one you are looking at. That is what makes it safe to start something slow and then go do something else.

The side panel follows the tab in front. Switch tabs and the chat switches with it — to that tab's conversation, or to a fresh empty one if it has none.

The sessions strip #

Above the chat, a row per tab that has a conversation: its live title, a pulsing dot while it is working, and how many messages it holds. Click a row to jump to that tab and its transcript; press × to end that session. It collapses to a single line when you want the room back.

Minimizing to the rail #

The header's collapse button closes the panel and leaves a small rail floating at the edge of the page — the same five tabs as icons, and the link's status dot. Click any of them and the panel comes back on that tab.

A run keeps showing itself while you are minimized: Chat carries a pulsing mark, the rail counts how many runs are live, and its edge picks up the working colour. It stays minimized until you reopen it.

The rail is drawn into the page, so it cannot appear on pages Browsentic is not allowed into — chrome:// pages, the Chrome Web Store and the new tab page. The toolbar icon and the right-click Open Browsentic item always work.

Knowing something is running when you are elsewhere #

While a conversation is working, its tab is marked in two places — a dot on the Browsentic toolbar icon, and a dot drawn onto the tab's own favicon — so a run you have scrolled away from is still visible in the tab strip.

Subtabs #

If a conversation opens a tab of its own, that tab joins the same session as a subtab and its work belongs to the same transcript. A run will not act in a tab another conversation has claimed — attempting it returns TAB_IN_USE.

Closing things #

Limits #

History #

Conversations are saved and named automatically. The History tab reopens any of them, on any tab.

The timeline #

Every action appears as it happens, with what it targeted and what came back.

See also #

• Instant commands — why some things answer before you finish reading them
• Skills — what decides how an instruction is handled
• internals/extension.md § Tab scoping — how a run stays in its own tab