Back to Support
features

Browser Clip Beta

Capture selected browser text as governed, review-only TurnkeyGTM context.

Browser Clip Beta captures only the text you deliberately select on an HTTP or HTTPS page. You review the passage and source metadata in TurnkeyGTM before anything is saved.

What the beta captures

  • selected text;
  • page title and source URL;
  • capture timestamp;
  • an optional note;
  • sensitivity and project labels.

The beta does not fetch the full page, forward browser cookies, capture screenshots, record the screen, or run in the background.

Install the unpacked beta companion

  1. Obtain the tools/browser-clip-extension directory from the beta build.
  2. Open chrome://extensions.
  3. Enable Developer mode.
  4. Select Load unpacked and choose that directory.
  5. Pin TurnkeyGTM Browser Clip if you want one-click access.

This is an unpacked beta companion, not a Chrome Web Store release.

Capture selected context

  1. Sign in to TurnkeyGTM.
  2. Open an HTTP or HTTPS page and select the useful passage.
  3. Open TurnkeyGTM Browser Clip and select Review clip in TurnkeyGTM.
  4. In the /clip review screen, inspect or edit the title, source URL, passage, note, sensitivity, and project label.
  5. Confirm that the selected passage and note may be processed by TurnkeyGTM's configured external AI providers.
  6. Select Save and process.
  7. Inspect processing on the document status screen.
  8. Open the knowledge review queue to approve, edit, or reject extracted proposals.

A clip’s extracted entities remain pending and absent from Active Memory retrieval until approved. The beta does not extract or save relationships for these proposals because relationship review is not available yet. Approving an entity publishes its search embedding; rejecting it removes any embedding.

Duplicate submissions

Submitting the same governed payload again returns the original document instead of creating a duplicate. Changing the passage, note, sensitivity, project label, title, or canonical source URL creates a distinct payload.

Privacy and governance boundaries

  • Tenant identity comes from your authenticated account and server-side membership, never from the extension payload.
  • The selected passage enters a minimal same-origin handoff page in a URL fragment. That page synchronously moves it to tab-scoped session storage and removes it from the URL before authentication or the review app loads. The review page consumes and deletes it.
  • Source URLs are normalized but never fetched by Browser Clip.
  • Tracking query parameters are currently retained; review the URL before saving if it contains sensitive values.
  • Sensitivity and project are labels in this beta, not access-control rules.
  • Selected passages and notes are processed by the external AI providers configured for TurnkeyGTM only after explicit confirmation.
  • Restricted sensitivity is rejected in this beta. Do not clip restricted data; a compliant provider policy is not yet available.

Current beta exclusions

  • full-page crawling;
  • screenshots or OCR;
  • offline capture queues;
  • mobile share targets;
  • private browser schemes;
  • Chrome Web Store distribution;
  • sensitivity-based access enforcement.
  • relationship extraction/review for clip proposals.

Troubleshooting

  • Nothing was captured: select non-empty page text before opening the extension.
  • Page is unsupported: Browser Clip accepts only http:// and https:// pages.
  • Selection is too large: reduce it below 20,000 characters.
  • Multiple organizations: the beta requires one active organization because it does not yet include an organization picker.
  • Processing failed: use the document status page error and retry controls.

Still need help? Contact our support team