> ## Documentation Index
> Fetch the complete documentation index at: https://explore.airia.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Browser Extension Configuration

> Configure and manage browser extension capabilities for your organization.

The Browser Extension interface allows administrators to configure AI agent capabilities that users can access directly from their web browsers. Set up standard actions and create custom workflows that integrate seamlessly into your users' browsing experience.

## Browser Extension Download

<CardGroup cols={2}>
  <Card title="Chrome Web Store" icon="chrome" href="https://chromewebstore.google.com/detail/airia/hcjkecanahplkmniojegmmjjijopbdma">
    Install for Google Chrome
  </Card>

  <Card title="Firefox Add-ons" icon="firefox" href="https://addons.mozilla.org/en-US/firefox/addon/airia/">
    Install for Mozilla Firefox
  </Card>
</CardGroup>

## Overview

Browser extension capabilities provide context-aware AI assistance that users can invoke while browsing. When configured, these capabilities appear as Quick Actions in the browser extension's chat sidebar, allowing users to interact with your agents without leaving their current webpage.

<Note>
  Browser extension capabilities are available to users with the Platform Admin, Admin, Read-Only Admin, and Project Admin roles.
</Note>

## Accessing Browser Extension Settings

1. Navigate to **Settings** in the Airia platform
2. Select **Extensions** from the sidebar
3. Click on **Chrome Extension** to view and manage capabilities

## Standard Capabilities

The browser extension includes three built-in capabilities that you can enable and configure:

### Summarize

Generates concise summaries of webpage content, helping users quickly understand long articles, documentation, or reports.

**Configuration:**

* **Agent Assignment**: Select which agent handles summarization requests
* **Context**: Automatically includes the current page content

### Key Points

Extracts main points from webpages in bullet format, ideal for research and information gathering.

**Configuration:**

* **Agent Assignment**: Select which agent extracts key points
* **Context**: Automatically includes the current page content

### Translate

Translates webpage content into different languages based on user requests.

**Configuration:**

* **Agent Assignment**: Select which agent handles translation requests
* **Context**: Automatically includes the current page content

### Configuring Standard Capabilities

For each standard capability:

1. Click **Assign Agent** or **Change Agent** to select an agent
2. Choose from your available agents in the dropdown
3. Click **View Agent** to review the agent's configuration in a new tab
4. All changes are saved together when you click **Save Changes**

<Tip>
  Assign agents specifically designed for each capability type to ensure optimal performance and accurate results.
</Tip>

## Custom Capabilities

Create custom capabilities tailored to your organization's specific workflows and use cases. Custom capabilities appear alongside standard capabilities in the Quick Actions menu.

### Creating a Custom Capability

1. Click **Add Custom Capability** in the Custom Capabilities section
2. Configure the following settings:

#### Display Name

The name users see in the Quick Actions menu. Choose a clear, action-oriented name (e.g., "Analyze Competitors", "Extract Contact Info").

#### Agent Selection

Select which agent powers this capability. The agent should be configured to handle the type of task this capability performs.

#### Mode

Choose how the capability accesses webpage content:

* **Page**: Includes the entire page content as context
* **Selection**: Only includes text the user has selected on the page
* **Page Source**: Provides the raw HTML source of the page

#### Initial Message

The prompt sent to the agent when users invoke this capability. This message:

* Can include instructions for how to process the content
* Should be clear about what the agent should do
* Can reference the page context that will be automatically included

**Example Initial Messages:**

* "Analyze this webpage and identify key competitors mentioned"
* "Extract all contact information from this page"
* "Summarize the technical specifications in a comparison table"

3. Click **Add** to create the capability

### Editing Custom Capabilities

1. Click the **Edit** icon next to any custom capability
2. Modify the settings as needed
3. Click **Save** to apply changes

### Deleting Custom Capabilities

1. Click the **Delete** icon next to the capability you want to remove
2. Confirm deletion in the dialog
3. The capability will be removed after clicking **Save Changes**

<Warning>
  Deleting a custom capability removes it from all users' browser extensions immediately after saving. This action cannot be undone.
</Warning>

## Saving Changes

All capability changes (standard and custom) are saved together in a batch operation:

1. Make all desired changes to your capabilities
2. Click **Save Changes** at the bottom of the page
3. A success message confirms the changes have been applied
4. Users will see updated capabilities immediately in their browser extensions

<Note>
  The Save button is only enabled when all required fields are filled and at least one change has been made.
</Note>

## Best Practices

### Agent Assignment

* **Specialized Agents**: Create agents specifically designed for each capability type
* **Testing**: Test agents in the platform before assigning them to browser extension capabilities
* **Performance**: Choose agents optimized for quick responses since users expect real-time interaction
* **Chat History**: Enable the **"Include the chat history"** option in AI steps for agents deployed to the browser extension. This maintains conversation context across interactions within the same browsing session.

### Custom Capability Design

* **Clear Names**: Use action-oriented names that clearly describe what the capability does
* **Focused Tasks**: Design capabilities for specific, well-defined tasks
* **Mode Selection**: Choose the appropriate mode based on what data the agent needs:
  * Use **Page** for analyzing entire documents
  * Use **Selection** for focused analysis of specific content
  * Use **Page Source** only when HTML structure is needed

### Initial Messages

* **Be Specific**: Provide clear instructions about what the agent should do
* **Set Expectations**: Include output format requirements (e.g., "in bullet points", "as a table")
* **Context Awareness**: Remember that page content is automatically included

## Use Cases

### Standard Capabilities

* **Research Teams**: Enable Summarize and Key Points for quick literature review
* **International Teams**: Enable Translate for multilingual content access
* **Content Teams**: Use all three for content analysis workflows

### Custom Capabilities Examples

* **Sales Teams**: "Extract company information" - captures company names, sizes, and industries
* **Legal Teams**: "Find compliance mentions" - identifies regulatory and compliance references
* **Support Teams**: "Diagnose error messages" - analyzes error logs and suggests solutions
* **Marketing Teams**: "Analyze competitors" - identifies competitive positioning and messaging

## Troubleshooting

<AccordionGroup>
  <Accordion title="Why can't users see the capabilities I configured?">
    Ensure that:

    * You clicked **Save Changes** after configuring capabilities
    * Users have the browser extension installed and are signed in
    * The assigned agents are active and accessible to users
    * Users have refreshed their browser or restarted the extension
  </Accordion>

  <Accordion title="A capability isn't working as expected">
    Check the following:

    * The assigned agent is properly configured and tested
    * The initial message provides clear instructions
    * The correct mode (Page/Selection/Page Source) is selected
    * The agent has appropriate permissions and tool access
  </Accordion>

  <Accordion title="How many custom capabilities can I create?">
    There is no hard limit on custom capabilities, but consider:

    * User experience: Too many options can be overwhelming
    * Maintenance: Each capability requires its own agent and testing
    * Best practice: Focus on 3-5 high-value custom capabilities
  </Accordion>

  <Accordion title="Can I disable a capability temporarily?">
    To temporarily disable a capability:

    * For standard capabilities: Unassign the agent and save
    * For custom capabilities: Delete it and save (you can recreate it later)
    * Consider communicating changes to users beforehand
  </Accordion>

  <Accordion title="What happens to active conversations when I change a capability?">
    * Changes take effect immediately for new invocations
    * Active conversations continue using the previous configuration
    * Users should start new conversations to use updated capabilities
  </Accordion>

  <Accordion title="The agent responds that it can't see webpage content">
    If your browser extension's agent is responding that it can't see any webpage content:

    * Verify that the **"Include the chat history"** option is enabled on all LLMs in the agent
    * This setting is required for the agent to access the page context that the browser extension automatically provides
    * You can enable this in the AI step within Agent Studio
  </Accordion>
</AccordionGroup>

## Enterprise Deployment

For organizations using Mobile Device Management (MDM) systems, the browser extension supports centralized configuration:

### MDM Configuration Options

* **Pre-defined Region**: Specify which Airia region users connect to
* **Custom Servers**: Configure custom API and authentication server hostnames
* **Lock Configuration**: Prevent users from changing connection settings

### Deployment Benefits

* **Consistent Configuration**: All users connect to the correct Airia instance
* **Security Compliance**: Ensure connections only to approved servers
* **Zero User Setup**: Extensions work immediately without manual configuration
* **Policy Enforcement**: Configuration cannot be changed by end users

<Note>
  MDM configuration is managed separately from capability settings. Contact your IT department or Airia support for MDM deployment guidance.
</Note>