Skip to content

Permission Explanations ​

AIPageGo keeps core page automation available after installation and asks for browser-data access only when a matching feature is used. Denying an optional permission does not disable normal page chat.

Requested at installation ​

PermissionPurposeBoundary
sidePanelShow chat and tools in Chrome's side panelDoes not read page data by itself
storageStore settings, conversations, tools, and runsAPI keys are excluded from IndexedDB and exports
scripting / activeTabInject or run tools on pages involved in a user taskSite policy and tool approval still apply
tabs / tabGroups / webNavigationTrack the active tab, multi-tab sessions, URL changes, and visible session groupsDoes not grant access to Chrome's history database
contextMenusProvide a right-click entry pointHandles only a user-selected action
<all_urls>Read or operate on the current page and match saved tools by URLNo background bulk upload; restricted pages cannot be injected
ws://127.0.0.1/* / ws://localhost/*Connect to a local Coordinator or MCP serviceLocal addresses only; connection and remote chat are user-controlled

Requested when used ​

Optional permissionTriggerIf deniedRevoke
bookmarksBookmark search and bookmark mentionsThat bookmark action is skippedSettings → Permissions or Chrome extension details
historysearchHistoryThat search is skippedSettings → Permissions or Chrome extension details
downloadsImage and XLSX downloadsNo file is createdSettings → Permissions or Chrome extension details
notificationsChange, success, or final-failure notices for local JobsThe Job still runs; no system notification is shownSettings → Permissions or Chrome extension details
debuggerExplicitly enabled advanced page-event recordingRecording degrades to the non-CDP backendChrome extension details

After a grant, AIPageGo retries the original operation once. If the Chrome API still fails, it reports the error and does not prompt in a loop. Coordinator and MCP cannot request permission for you; they receive a machine-readable PermissionDenied result.

Browser permissions and dangerous-tool approval are independent gates.

Connector network access ​

Connectors require no additional Chrome permission. HTTPS requests use the extension's existing page-network capability and do not trigger another browser permission prompt. Webhook and Feishu/Lark Base targets and credentials are user-configured. AIPageGo provides no public relay and never sends page or chat content merely because a connector exists.

Job notifications include only the Job name, pinned version, terminal state, and a bounded error code or change count. They exclude URL queries, inputs, page text, and output.

See also: Privacy Policy · Connectors and secure sharing · Configuration

MIT License