Chrome Connector

Use logged-in Chrome tabs with Kendr Desktop.

The Kendr Chrome Connector is an optional extension plus local Native Messaging host. It lets approved Desktop tasks list tabs, read bounded page snapshots, capture screenshots, and perform browser actions in Chrome tabs where you are already signed in.

Download connector Download page

Optional Chrome profile Local bridge Approval gated

What the connector is

Kendr Desktop already includes its own built-in browser worker for ordinary web tasks. The Chrome Connector is the separate path for tasks that need your real Chrome session, such as a logged-in SaaS dashboard, internal console, or documentation site behind an account.

Extension

Runs inside Chrome

Lists tabs, captures visible state, and executes approved browser actions in pages you permit.

Native host

Stays on your computer

Connects the extension to Kendr Desktop through Chrome Native Messaging without exposing the local API token to extension JavaScript.

Desktop connector

Appears in Kendr tools

Kendr can request tab snapshots and browser actions through the same local connector approval flow as other tools.

Built-in browser

Still the default

Use the built-in browser for normal browsing automation. Use Chrome only when the existing signed-in profile matters.

Install from kendr.org

The current connector bundle is a developer preview. Packaged Kendr releases should eventually install and register the native host automatically.

1
Install Kendr Desktop
Download and open the current Desktop build from kendr.org/download.html.
2
Download the connector
Download kendr-chrome-connector-0.1.0-dev.zip and extract the archive.
3
Load the extension
Open chrome://extensions, enable Developer mode, choose Load unpacked, and select the extracted chrome-extension folder.
4
Register the native host on Windows
Copy the extension ID from Chrome, then run the installer script from the extracted bundle.
5
Connect from Kendr
Open Kendr Desktop, go to Connectors, and enable Chrome. The extension status should show that the native host is connected.

powershell -ExecutionPolicy Bypass -File .\chrome-native-host\install-windows.ps1 -ExtensionId <extension-id>

Chrome itself

Kendr does not redistribute Google Chrome. Install Chrome from google.com/chrome, then install the Kendr connector bundle from kendr.org.

Connector capabilities

Tool	Purpose	Approval expectation
list_tabs	See open tab IDs, titles, URLs, and active state.	Read-only.
active_tab	Find the currently active Chrome tab.	Read-only.
snapshot	Read a bounded page snapshot with element references for later actions.	Read-only.
capture_screenshot	Capture the visible tab image for visual inspection.	Read-only.
navigate	Move a tab to a URL.	Approval required.
click	Click a referenced element from a recent snapshot.	Approval required.
type	Type text into a referenced element.	Approval required; sensitive typing is refused by the preview connector.
press_key	Send a browser key press such as Enter or Escape.	Approval required.

Privacy and safety boundary

The extension does not export Chrome cookies, local storage, session storage, or saved passwords.
The extension never receives the Kendr Desktop loopback bearer token; the native host keeps that credential local.
Snapshots are bounded and meant for task context, not full-page archival scraping.
Actions that change a tab, type text, click controls, or navigate should pass through Kendr's approval flow.
Use the connector only for Chrome profiles and sites you trust Kendr Desktop to operate.

Chrome references

The connector follows Chrome's extension platform boundaries. Chrome documents the Native Messaging manifest and host registration model in the Native Messaging guide, and documents tab metadata and permissions in the Tabs API reference.