Bookmarklets are such an underrated feature. It's super convenient to inject and test scripts on any page. Seemed like the perfect low-friction entry point for people to try it out.
Spent some time on that UX because the concept is a bit hard to explain. Glad it worked!
I'd be really interested in feedback on the security model of client-side agents giving extension-bridge access, and taking questions on the implementation!
Currently, the extension only has access to the active tab when the task starts (configurable) and any new tabs it opens — all automatically placed into a dedicated tab group. It won’t touch other existing tabs.
Are you looking for something like scoping the agent to a predefined tab group?
Scoping to a dedicated tab group is a smart approach for sandboxing. The activeTab permission model already limits access nicely, but combining it with tab groups adds a visible boundary that users can actually see and trust. Would be great if Chrome's extensions API gave more granular tab group controls natively.
