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

# AI Assistant

> Use the Extensy Doc Assistant — an in-page AI chat widget — to get instant answers about extension development.

# AI Assistant

The **Extensy Doc Assistant** is an AI chat widget embedded directly in this documentation site. Ask it anything about building Chrome extensions with Extensy and get answers grounded in this documentation — without leaving the page.

## How to use it

The assistant appears as a chat widget on every page of the docs. To use it:

**1. Open the chat widget**

Click the chat icon in the bottom-right corner of any documentation page to open the assistant panel.

**2. Ask your question**

Type your question in plain English. Be specific — the more context you provide, the more precise the answer.

**Examples of good questions:**

* "What permissions do I need to read cookies from a specific domain?"
* "How do I send a message from my content script to the background service worker?"
* "Why is my popup closing before my async function finishes?"

**3. Follow up or refine**

The assistant maintains context within a session, so you can ask follow-up questions or ask it to clarify a previous answer.

## What the assistant can help with

> **Chrome API usage**
>
> Questions about specific Chrome APIs — `chrome.storage`, `chrome.tabs`, `chrome.runtime`, `declarativeNetRequest`, and more.

> **Manifest V3 configuration**
>
> Help with `manifest.json` fields, permission declarations, service worker setup, and MV3 migration patterns.

> **Extensy-specific features**
>
> Guidance on prompting strategies, how credits work, exporting your ZIP, and iterating on generated code.

> **Debugging common errors**
>
> Help diagnosing common issues like permission errors, content script injection failures, and service worker lifecycle problems.

## How it works

The assistant is powered by **Google Gemini 1.5 Flash** with a custom system prompt that scopes its responses to information found in this documentation. This keeps answers accurate and Extensy-focused rather than drawing on generic web knowledge that may not apply to your use case.

> [!NOTE]
>
> If the assistant can't find a reliable answer in the documentation, it will tell you — and recommend joining the [Extensy Discord community](https://discord.gg/HB6DZYws) where the team and other developers can help directly.

## Limitations

The assistant works best for questions that are directly addressed in this documentation. Be aware of the following:

> **It doesn't have access to your code**
>
> The assistant cannot read your generated extension files, inspect your Chrome installation, or access your Extensy account. For questions that require looking at specific code, paste the relevant snippet directly into your message.

> **It may not reflect the very latest changes**
>
> The assistant's knowledge is based on this documentation. If a feature was released very recently, the docs may not yet reflect it. Ask on [Discord](https://discord.gg/HB6DZYws) for the most current information.

> **It is scoped to Extensy and Chrome extension development**
>
> The assistant is intentionally limited to extension development topics. Questions about unrelated technologies or general programming will receive a redirect to a more appropriate resource.

> [!TIP]
>
> For complex debugging sessions, combine the assistant with the Chrome DevTools **Extensions** panel and the service worker inspector at `chrome://extensions` → **Inspect views: service worker**.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.