extension_add_feature
Plan the surface before adding an options page, a popup, a side panel, a content script, a devtools panel, a new tab page or a background script to an existing extension.
Quick start
Add an options page to this extension
Asked to add an options page, the agent plans the surface, writes it, validates the manifest and proves it in a dev session.
How the agent uses it
It answers with the manifest additions, the files to create and the catalog template to copy from, and modifies nothing: write what the plan says, then validate the manifest and run extension_dev.
Reference
| Group | local, on by default |
| Tier | Create and build |
| Needs | none |
| Read only | yes |
| Destructive | no |
| Idempotent | yes |
| Reaches the open web | no |
Inputs
| Input | Type | Required | Default | What it does |
|---|---|---|---|---|
projectPath | string | yes | Extension project root | |
feature | "sidebar" | "popup" | "options" | "content-script" | "background" | "newtab" | "devtools" | yes | Feature surface to add | |
framework | "react" | "vue" | "svelte" | "preact" | "vanilla" | no | "react" |
Next
- MCP server: install, the two groups and the session gates
- Install in your client
extension_build: Build a browser extension for production.extension_create: Create a browser extension project from a template in the extension.dev catalog.extension_docs_search: Find the docs page to cite before answering any question about a WebExtension API, a manifest key, a permission, or a difference between Chrome, Firefox, Edge and Safari.extension_templates: Browse the extension.dev template catalog.