llm-wiki for Chrome

Public source · local execution · explicit tab grants

Give your local agent one tab—not your whole browser.

LLM Wiki for Chrome gives a local agent bounded control of tabs you explicitly share. Every grant is visible, tied to one exact tab and origin, and revocable from the side panel.

Install the development build View source How collaboration works
Explicit tabs Fixed MCP tools No persistent host access Local Native Messaging

You can see exactly what the agent controls

A shared tab gets a green outline, an LLM WIKI • CONTROLLED marker, an ON toolbar badge, and a side-panel entry. The agent sees the grant immediately through the local connector—no port, pairing code, or page OAuth flow.

LLM Wiki for Chrome connected to one explicitly shared llm-wiki.net tab, with the controlled-tab marker and local connector status visible.
One explicitly shared tab. Green means the local agent can act on that tab; Stop revokes it.

Development installation

Install the companion, then load the extension

There is no stable package or Chrome Web Store listing yet. The current public build is installed from the HEAD formula in nvk/tap and loaded unpacked.

1

Install the native companion

brew install --HEAD nvk/tap/llm-wiki-chrome
llm-wiki-chrome install

Chrome starts the allowlisted Native Messaging host on demand. No daemon or background service is installed.

2

Get the extension path

llm-wiki-chrome extension-path

Copy the printed path. It points at the exact extension bundled with the installed companion.

3

Load it in Chrome

  1. Open chrome://extensions.
  2. Turn on Developer mode.
  3. Click Load unpacked.
  4. Select the path from step 2.
  5. Pin LLM Wiki for Chrome to the toolbar.
4

Connect Codex through MCP

codex mcp add llm-wiki-browser -- \
  llm-wiki-chrome mcp-server

Start a new Codex session after registration. Other MCP hosts can use the same stdio command: llm-wiki-chrome mcp-server.

5

Verify the local installation

llm-wiki-chrome doctor

healthy: true verifies the package and registration. connected: true appears while Chrome has the native port open.

Already using a targeted adapter?

Provider-specific llm-wiki adapters can call the same local client directly. They still own authentication, planning, revision locks, recovery, and independent verification.

Click to collaborate

Share a page in five steps

1 Open the target Navigate to the HTTPS page you want the agent to use.
2 Click the toolbar icon This Chrome user gesture creates authority for only the active tab.
3 Confirm the marker The tab turns green and the side panel reports Connected—agent notified.
4 Tell the agent what to do The agent lists shared tabs and uses fixed tools against the selected grant.
5 Stop when finished Use Stop, close the tab, or leave the origin to revoke its grant.

Share more than one tab

Click the extension on additional tabs to build an explicit workspace of up to 16 grants. Unrelated tabs are never enumerated.

Mutations stay governed

Protected actions still require local confirmation. Consequential provider workflows should use a targeted adapter with plan binding and read-back verification.

Fixed capabilities, not arbitrary browser code

Inspect

Bounded accessibility snapshots, element geometry, viewport/region/full-page screenshots, waits, and private diagnostics.

Interact

Semantic click, hover, type, select, drag, key, scroll, tab focus, and same-origin navigation through typed tools.

Transfer deliberately

Uploads and downloads work only inside explicitly registered local roots, with path, completion, danger-state, and hash checks.

Stay visible

Green page outline, controlled-tab pill, toolbar badge, tab group, side-panel status, and content-free completion notices.

Fail closed

Exact collaboration ID, URL, origin, program hash, capability, limits, deadline, and focus are validated before execution.

Keep content local

Page data is returned only to the calling local agent for the active request. The extension panel and repository never store or display it.

Security boundary

The click is the permission boundary

What the extension does

  • Grants one exact active tab after your toolbar click.
  • Shows a persistent visual marker while control is active.
  • Uses a local, allowlisted Native Messaging connection.
  • Accepts only versioned, schema-validated typed operations.
  • Revokes grants on stop, close, or cross-origin navigation.

What it refuses

  • No arbitrary JavaScript or raw CDP method tool.
  • No <all_urls> or persistent host permissions.
  • No ambient browsing or unrelated-tab enumeration.
  • No natural-language execution inside the extension.
  • No repository storage of page content, credentials, plans, or results.

Public source does not make runtime data public. Tab grants, page content, credentials, private result slots, and Native Messaging sockets stay on the local machine. Review the security model before enabling consequential workflows.

Quick checks

No tabs are exposed

Open the target HTTPS page and click the pinned toolbar icon. A side-panel button cannot manufacture Chrome's required user gesture.

Connector is offline

Run llm-wiki-chrome install, reload the unpacked extension, then run llm-wiki-chrome doctor.

The agent cannot see a new grant

Confirm the side panel says Connected—agent notified. Restart the MCP client session if it was registered after the agent started.

Read the full README Report an issue