browser-extension

Browser Extension

Control the user's real browser (Chrome, Edge, Brave, Firefox, …) through the Wolffish extension. This operates in the user's actual browser — their cookies, logins, extensions, and open tabs are all available. Several browsers can be connected at the same time. The working loop is snapshot → act by uid → read the aftermath line, and when something in the setup is missing the capability can diagnose itself (ext_doctor) and fix most of it (ext_fix).

Tool Naming

All tools use the ext_ prefix. The wire protocol translates these to browser_ commands. For example ext_navigate sends browser_navigate to the extension.

Multiple browsers

The extension can be connected from several browsers at once (e.g. Chrome and Edge). Every connected browser is a fully separate world: its own tabs, tab ids, windows, cookie jars, logins, and its own debugger sessions.

• One browser connected — nothing to do; every ext_* tool targets it automatically.
• Several connected — each conversation drives exactly one browser at a time. Pick it with ext_use_browser (the choice sticks for the rest of the conversation; call it again to switch). Until a browser is picked, ext_* tools return an error listing the connected browsers.
• How to pick: if the user named a browser ("open it in Edge") or the context makes it obvious (the site is logged in only in Chrome, earlier in the conversation you were working in Brave), call ext_use_browser yourself and briefly say which browser you're using. If there is no signal which browser the user means, ask them before acting.
• Profiles: two Chrome profiles are two separate connections with separate logins. ext_browsers reports each profile's signed-in email — use it to tell them apart ("work" vs "personal") and pass an email fragment to ext_use_browser when the user means a specific profile.
• ext_browsers lists what is connected (name, version, OS, profile email, selection key) — check it when unsure what's available.
• Selection keys are stable while the app runs: a browser that reloads or reconnects keeps its key (chrome-2 stays the same profile). After an app restart keys may be assigned afresh — re-check ext_browsers rather than assuming.
• Never mix ids across browsers: a tabId from ext_tabs_list in Chrome is meaningless in Edge. After switching browsers, re-list tabs before acting on them.