Chrome Permission Audit

Chrome 'sidePanel' permission vs on-screen overlays: UX & privacy differences.

Compare Chrome's native sidePanel API (used by Sider, Monica, and Copilot) with on-screen selection overlays like Vezz me—covering viewport space, context scope, and permissions.

Best fit

Best for readers and developers comparing sidebar AI extensions (`sidePanel`) against inline on-screen overlays.

Technical Manifest Audit

Permission specification & risk profile.

Review how Chrome enforces sidePanel in Manifest V3 and how to tell legitimate user-triggered extensions apart from intrusive tools.

Risk level: LowersidePanel
Chrome install-time warning
None by itself (usually paired with host_permissions and scripting)
Manifest V3 declaration
{
  "manifest_version": 3,
  "permissions": ["sidePanel"],
  "side_panel": {
    "default_path": "sidebar.html"
  }
}
Legitimate uses vs. red flags
What to verify before granting this permission to an AI browser tool.

Legitimate AI reading uses

  • Hosting a persistent chat drawer beside the browser viewport
  • Keeping a multi-tool workspace open while switching between tabs

Red flags to watch for

  • Automatically reading every new tab's DOM as you switch tabs while the side panel stays open
  • Consuming 350–450px of horizontal screen width on laptops where documentation and code need full width
Step-by-step workflow

How to run this workflow in place.

1

Check what happens when you switch tabs

Because a global Chrome `sidePanel` stays open across tab switches, check whether the extension automatically ingests every tab you click into.

2

Measure horizontal viewport loss

On a 13-inch or 14-inch laptop, a 400px sidebar cuts ~30% of your reading width, forcing tables and code blocks to wrap or scroll.

3

Compare eye-movement distance

An on-screen overlay sits inches from your highlighted sentence so you can verify claims against the source immediately.

Key details

Why this approach works better than switching tabs.

Why sidePanel became popular—and where it creates friction
Chrome introduced the `chrome.sidePanel` API so extensions could build persistent chat apps inside the browser frame.
  • Great when you want an always-open chatbot that persists across unrelated tabs
  • Disruptive when you want to read a dense article, paper, or API doc in its native layout
  • Separates the AI explanation from the specific paragraph that prompted your question
Why Vezz me uses an on-screen overlay instead of a sidebar
Reading works best when the explanation comes to your cursor, rather than pulling your eyes to the far edge of the monitor.
  • Zero screen real estate used while you are reading normally
  • Panel appears next to your selection when you press Ctrl+Shift+X and auto-hides or closes when you're done
  • Supports Chrome and Firefox with a consistent, customizable floating panel
Frequently asked questions

Common questions about chrome permission audit.

Is the sidePanel permission dangerous?

The `sidePanel` permission itself is low risk—it only lets an extension render UI inside Chrome's side drawer. The privacy question is whether an open sidebar automatically reads the content of every tab you switch to, or waits for you to select text and ask.

Why doesn't Vezz me use a sidebar?

Because sidebars shrink your reading area and pull your eyes away from the source passage. Vezz me places a compact, movable answer card right beside the text you highlighted.

Related workflows & guides

Explore connected pages.

Available for Chrome and Firefox

Ready to try this workflow on your own reading?

Install Vezz me free, highlight text on any webpage, and press your customizable shortcut (default: Ctrl+Shift+X or Cmd+Shift+X on Mac) to get an answer right beside the source.