Chrome extension

Plan availability: This integration is available on the Agentic plan. Team plan customers can upgrade in Settings → Billing.

The Chrome extension lets you capture observations from any web page you have open. If a CRM ticket shows a great customer outcome, a project doc captures a tough decision well-handled, or a call recap surfaces an escalation, you can record it as an observation in two clicks — without leaving the tab.

This article covers what the extension does, how to install it, signing in, day-to-day use, what gets sent to Performance Blocks, privacy and site permissions, disabling per-site permissions, and troubleshooting.

What the Chrome extension does

The extension adds Henry agent capture to your browser toolbar. The core capabilities are:

1. Quick capture from any tab. Click the toolbar icon, write a short observation, choose the employee, and submit. The current page URL and a short context snippet are attached automatically.
2. Selection capture. Highlight text on a page, right-click, and choose Capture observation with Henry. The selected text becomes the seed for the observation.
3. AI-assisted draft. Henry can read the visible page (only when you click the capture button — not in the background) and pre-draft a candidate observation. You review, edit, and submit.

The extension is a thin client. The capture form lives in a popup; the actual write happens against the Performance Blocks API once you submit.

Prerequisites

Before installing, confirm:

• Your org is on the Agentic plan.
• An org admin has enabled henryAgentEnabled and henryAgentChrome in Settings → Features.
• You are using Google Chrome, or another Chromium-based browser that supports Chrome extensions (Edge, Brave, Arc).

If henryAgentChrome is greyed out in Settings, the master henryAgentEnabled toggle is off — turn that on first.

Installing the extension

The extension is distributed through the Chrome Web Store.

1. Open the Chrome Web Store and search for the Performance Blocks extension.
2. Click Add to Chrome.
3. Review the permissions Chrome shows you and click Add extension to confirm.
4. The extension icon appears in your Chrome toolbar. If it is hidden in the puzzle-piece overflow, click the puzzle-piece icon and pin the extension so it's always visible.

Unlike Slack and Teams, there is no admin install step — the extension is per-user. Each person installs it themselves on every browser profile they want to use it from. (If you use Chrome on a work laptop and a personal laptop, install it twice.)

If your organization uses Chrome Enterprise, an admin can pre-deploy the extension to every managed device through the Google Admin console. Ask your IT team if this is desired.

Signing in

The first time you click the extension icon, you are prompted to sign in.

1. Click the extension icon.
2. The popup shows a Sign in button. Click it.
3. A new tab opens to the Performance Blocks sign-in page. Sign in with your usual credentials (or SSO).
4. The browser is redirected back; the extension popup updates to show your name and team.

The session persists across browser restarts. If you sign out of Performance Blocks in the web app, the extension session is also invalidated and you'll be asked to sign in again the next time you open the popup.

Using the extension

There are three ways to capture an observation. Use whichever fits the moment.

From the toolbar popup

1. Click the extension icon in the toolbar.
2. The popup opens with a small form.
3. Choose the employee the observation is about. The dropdown autocompletes from your team.
4. Type the observation. Keep it short — the goal is to record what happened, not to write a paragraph.
5. Optionally, attach tags or blocks.
6. Click Save.

The current page URL is recorded as the source. You can review captured observations in the web app under the employee's profile.

From a text selection

1. On any web page, highlight the text you want to capture.
2. Right-click and choose Capture observation with Henry from the context menu.
3. The popup opens with the selected text pre-filled in the observation field.
4. Choose the employee, edit if needed, and save.

This is the fastest path when the source content already exists on the page (a customer email pasted into a CRM, a comment on a ticket, a quote from a transcript).

With Henry's AI draft

If you want Henry to do the first pass:

1. On the page you want to capture, click the extension icon.
2. Click Draft from page. Henry reads the visible page content and proposes a candidate observation.
3. Review the draft. Edit anything that's off.
4. Choose the employee (Henry will guess if a person is named on the page) and save.

The AI draft only runs when you explicitly click the button. The extension does not send page content to the server in the background.

Where captured observations go

Every observation captured by the extension lands in Performance Blocks identically to one captured in the web app:

• It shows on the employee's profile timeline.
• It is attributed to you as the recorder.
• It includes the page URL as the source link.
• It is searchable, filterable, and citable in summaries and reviews.

Henry can pre-draft from the page context, but every observation is reviewed and submitted by a human. Nothing is recorded silently.

Privacy and site permissions

The extension is designed to be conservative about what it sends to Performance Blocks. Three rules:

1. Only pages you explicitly capture are sent. The extension does not log your browsing history, page titles, or content unless you click the capture button (or use the right-click context menu) on that page. There is no background telemetry of pages visited.
2. Page content is sent only when you ask Henry to draft. The simple capture popup sends only what you type plus the URL. The "Draft from page" action is the only path that sends visible page text to the server.
3. Site permissions are scoped. The extension uses Chrome's activeTab permission, which means it only has access to a tab when you click the extension icon on that tab. It cannot read pages you have not interacted with.

If your team needs an extra layer of restriction (for example, never let the extension run on certain internal domains), Chrome lets you disable site permissions per host.

Disabling site permissions for specific hosts

1. In Chrome, open chrome://extensions.
2. Find the Performance Blocks extension and click Details.
3. Scroll to Site access. Set it to On click (the default and recommended setting) or specify the exact sites where the extension is allowed to run.
4. To disable on a specific site, navigate to that site, click the puzzle-piece icon, find the extension, and choose Don't allow on [site].

This is useful for sites with sensitive content where you never want the extension active.

Disabling and removing the extension

To disable temporarily:

1. Open chrome://extensions.
2. Toggle the extension off.

The icon will grey out and clicks won't open the popup. Toggle it back on when you want it again.

To remove entirely:

1. Right-click the extension icon and choose Remove from Chrome.
2. Confirm.

Removing the extension does not delete any observations you've already captured. Your existing observations remain in Performance Blocks.

Troubleshooting

Common issues and what to do.

"The extension popup is blank"

Usually a session issue:

• Try closing and reopening the popup.
• Click Sign in if the popup is showing the signed-out state.
• If the popup still won't load, disable and re-enable the extension from chrome://extensions.
• As a last resort, remove and reinstall.

"Right-click 'Capture observation' is missing"

The context menu item only appears when text is selected. Highlight some text first, then right-click.

If the menu item is still missing:

• Confirm the extension is enabled in chrome://extensions.
• Confirm site permissions allow the extension to run on the current page (see the Site access section above).
• Reload the page and try again.

"Draft from page returns nothing useful"

The AI draft works best on pages with clear narrative content (a CRM note, a doc, a comment thread). It is less useful on dashboards, listings, and apps where the visible content is mostly UI chrome.

If you get poor drafts, switch to the regular popup or selection capture and write the observation yourself.

"The wrong employee is being suggested"

The employee suggestion is a best-effort guess based on names visible on the page. It is not authoritative. Always review the dropdown selection before saving and pick the right person manually if needed.

"I'm getting permission errors when saving"

If saving an observation returns a permission error:

• Confirm you are signed in as the right user. Sign out and back in if unsure.
• Confirm the employee you selected is in your team scope (i.e., a direct or indirect report, or someone you have observation rights on).
• If the error persists, the diagnostics view in Settings → Integrations → Chrome extension shows your recent capture attempts and the error response.

"The extension stops working after a Chrome update"

Chrome updates occasionally invalidate extension sessions. Sign in again from the popup. If the extension itself doesn't load, remove and reinstall from the Chrome Web Store.

Related

• Meet Henry
• Slack integration
• Integrations overview