SESSIONS & CONTROL
When another extension stops a tab from sharing
Tallylamp Link shows this message when a page holds a frame from one of your other extensions. Chrome makes that rule, and Tallylamp Link can't lift it. The usual fix is to move the other extension out of the way. A Chrome flag can also switch the rule off, but it has a real security cost, and this page says exactly what that is.
What Chrome is refusing
Many extensions draw inside the pages you visit. A password manager puts a small frame next to sign-in fields to show its autofill menu. Grammar checkers, translators and AI sidebars do the same. The frame loads from the extension itself, at an address that starts with chrome-extension://, and you often can't see it.
Chrome lets an extension debug a tab only if it may open every frame in that tab. Extensions may not open each other's pages, so one frame from another extension is enough for Chrome to refuse the whole tab. Chrome's own error says "Cannot access a chrome-extension:// URL of different extension".
The rule keeps applying after you share. If a frame turns up later, Chrome ends the share at once. Password managers often add theirs when a sign-in field gets focus, and an agent clicks into fields all the time. So a tab can share fine and then stop when the agent reaches a login form.
Move the other extension out of the way
Each fix below keeps that extension's frame out of the page. None of them weakens Chrome.
Find the extension
If the panel shows Show that extension, press it. Tallylamp Link has worked out which one it is. Open your extensions means it couldn't narrow it down, so look for the ones that run on this site.
Set its site access to On click
On the extension's Details page, change Site access to On click. It then runs on a page only after you click its toolbar icon. On specific sites works too, as long as this site isn't on the list.
Reload and share
Reload the page so the frame goes away, then press Share this tab. Leave that extension's icon alone while the tab is shared. Clicking it lets the frame back in, and sharing stops.
| Option | What it costs |
|---|---|
| Turn the extension off while the agent works | It's off in every tab until you turn it back on. |
| Keep a second Chrome profile for agent work, with only Tallylamp Link installed | You sign in to the agent's sites again in that profile. |
| Use a browser on your Tallylamp server instead | It connects from your server's IP address, and some sites answer that with a verification page. |
The Chrome flag, and what it costs
This one works. It also switches off a Chrome security rule for every extension in every tab, so read the whole section before you turn it on.
The flag is called Extensions on chrome-extension:// URLs. In Chrome, open chrome://flags/#extensions-on-extension-urls, set it to Enabled and relaunch. In a test on Chrome 153, a tab holding another extension's frame shared normally, and it stayed shared when a new frame arrived. Other Chromium browsers weren't tested. Tallylamp Link can't read Chrome's flags, so it can't warn you before you share.
| What | With the flag on |
|---|---|
| Other extensions' frames and pages | Any extension allowed to debug tabs can debug these too. In the same test, a debugger session on the tab read the text inside another extension's frame. That frame could be a password manager's autofill menu, which can show the accounts you've saved for the site. |
| An agent in a shared tab | Tallylamp Link 0.8.4 and newer detach from the other extension's frame before the agent can use it, then say in the panel that the flag is probably on. Older versions pass that frame to the agent's tools like any other. |
| When it applies | All the time, in every tab, whether anything is shared or not. It stays on until you turn it off. |
A second Chrome profile gets you the same result with the rule still on, so try that first. If you turn the flag on anyway, do it in a profile with no password manager, and switch it off when the job is done.
Why Tallylamp Link doesn't remove the frame
Tallylamp Link could delete the other extension's frame and then share the tab. That works when the frame is already in the page. It fails when the frame comes back. In testing, Chrome ended the share even when a script removed the new frame the moment it appeared. Deleting it would also break the other extension on that page without telling you.
Docs behind this guide
Based on Tallylamp's documented behaviour. See the source for API details and release-specific settings.