Why AGNURA Requests activeTab, tabs, scripting, storage, tts, and Site Access

Chrome will show permissions when you install AGNURA AI Assistant. Those labels look technical. This guide translates each one into what AGNURA actually uses it for.

You will see permissions such as activeTab, tabs, scripting, storage, and tts, plus host access for sites and for app.agnura.com. Broad site access (<all_urls>) is the biggest trade-off. It lets AGNURA analyze the prospect site in your active tab without an AGNURA analysis proxy.

For what data stays local vs what leaves when you click an action, read AGNURA Privacy in Plain Language. For the full product map, read What Is AGNURA?.

Prerequisites

Before this guide helps, you need:

• Chrome (or a Chromium browser that can install from the Chrome Web Store)
• Willingness to open the extension popup on a normal https page after install
• Optional: Settings → General open so you can see toggles such as Speak selected text and channel activation

You do not need AGNURA credits to understand permissions. You only need sign-in and credits when you use AI generate or rewrite features.

Direct answer

AGNURA asks for permissions so it can:

1. Work on the tab you are looking at when you open the popup or start a job
2. Inject helpers on demand for analysis, Apollo capture, or Speak selected text
3. Save settings, templates, caches, and Apollo rows on your machine
4. Speak highlighted text with Chrome text-to-speech when you turn that setting on
5. Fetch sitemaps and related public URLs for sites you analyze
6. Call app.agnura.com managed AI when you start an AI action while signed in

AGNURA does not use these permissions to auto-send Gmail, LinkedIn, WhatsApp, or Reddit messages. You review drafts. You send or publish in the host app.

Permission by permission

activeTab

What Chrome means: The extension may act on the tab that is focused when you invoke it (opening the popup counts as that kind of user action for many flows).

Why AGNURA needs it: Website research and related popup actions are built around the page you are viewing, not a silent scan of every open tab.

What it is not: Always-on reading of every tab in the background.

tabs

What Chrome means: The extension can read tab metadata such as id and URL.

Why AGNURA needs it: The background worker needs the active tab’s URL and id so it can derive the site origin, inject scripts into the right tab, and match messages from that tab.

What it is not: A timer that lists all your tabs and uploads them to an AGNURA server. AGNURA does not upload browsing history or tab lists; sync is for account settings when signed in.

scripting

What Chrome means: The extension can run scripts in pages when allowed.

Why AGNURA needs it: AGNURA injects helpers when you start a job, for example:

• Analysis helpers when you run website research on the active tab
• Apollo helpers when you click Get Apollo Data
• Speak helpers into the active http(s) tab after you enable Speak selected text

Why not inject everywhere all the time? A static content script on every website would be heavier. On-demand injection keeps Speak and analysis closer to actions you start. Channel menus on Gmail, LinkedIn, WhatsApp Web, and Reddit use declared content scripts for those sites only.

storage

What Chrome means: The extension can save data in Chrome storage.

Why AGNURA needs it: Settings, prompts, templates, analysis caches, sitemap snapshots, Apollo rows, Generate Post criteria, and related local caches live in chrome.storage.local on your profile. That can include a signed-in session when you sign in.

What it is not: full dump of research caches. Account settings can sync when signed in. Clearing extension data removes local stores under Chrome’s normal rules.

tts

What Chrome means: Text-to-speech.

Why AGNURA needs it: Speak selected text (off by default in Settings → General) can read a highlight aloud with Chrome’s TTS path and the OS default voice.

What it is not: Sending the highlight to managed AI as an analytics upload. Voice to Text is separate. It uses the browser speech API on the site you are using and does not add a new extension microphone permission.

Site access (<all_urls>)

What Chrome means: The extension may contact many websites, not only one fixed domain.

Why AGNURA needs it: When you analyze a prospect site, the extension may fetch that site’s sitemap, nested sitemap URLs, optional same-origin product JSON, optional Archive.org hints, and (from the tab context) same-origin contact or about pages to find emails or phones. Without broad host access, AGNURA could not analyze arbitrary customer sites from your browser unless it sent traffic through an AGNURA proxy (which the current product does not).

Trade-off: This is a powerful permission. Treat it as the cost of “research this site I opened” without a central analysis server. Review the live Privacy Policy and this guide if your company policy requires narrower host lists. A private fork could lock hosts to known domains, but then sites outside that list would not analyze.

AGNURA app host access (https://app.agnura.com/*)

What Chrome means: The extension may talk to the AGNURA app API host.

Why AGNURA needs it: AI generate and rewrite features call app.agnura.com managed AI with your signed-in session when you click those actions.

What it is not: A personal OpenAI key paste. AI is billed as AGNURA credits (free allotment or Pro). Analysis and the rules-based SEO audit do not use managed AI by themselves.

Channel scripts vs analysis permissions

Gmail, LinkedIn, WhatsApp Web, and Reddit each have a content script match for that site’s compose UI. Local toggles such as Activate Gmail turn the AGNURA menus on or off for you. Those toggles are settings, not new Chrome permission prompts.

Website analysis on other https sites relies on the active-tab + scripting + site-access path above, not on a permanent “inject on every page load” script for the whole web.

What success looks like

After install you should be able to:

1. Open AGNURA on a normal https page and run analysis without a surprise “missing permission” failure for the declared set
2. Save Settings → General and see them stick after you close the popup
3. Use AI actions only after you sign in (if you choose to)
4. Leave Speak selected text off until you want it
5. Confirm drafts still require your review before send or publish in Gmail, LinkedIn, WhatsApp Web, or Reddit

Limits and non-goals

Permissions do not mean AGNURA will:

• Auto-send messages or posts
• Read your full browsing history on a schedule
• Provide a hosted CRM or team sync in the current product
• Guarantee that every site’s DOM will always expose contacts or schema the same way
• Replace your company’s policy review for prospect data, Apollo CSV exports, or webhook Add Lead posts

If Chrome shows a permission warning on update, it usually means the new version asks for new or broader access than you already granted. Adding a content script for a host already covered by existing site access normally does not force that kind of re-approval.

Related guides

• What Is AGNURA?: product scope
• AGNURA Privacy in Plain Language: local storage vs outbound calls
• Privacy Policy: legal wording

Soft next step

If these trade-offs match how you work, install from the Chrome Web Store, open Settings, and enable only the channels and Speak option you need before you research a live prospect site.

Add to Chrome