fix(extension): change Firefox add-on id to browser-agent@kilo.ai

[iscekic]

Why

Product can't submit the extension to the Firefox store: the current gecko id kilo-extension@kilocode.ai collides on AMO. It also still uses the retired kilocode.ai domain while the rest of the extension is on kilo.ai.

What

• Rename the Firefox add-on id to browser-agent@kilo.ai in wxt.config.ts (source of truth for the manifest).
• Update the one e2e test that hard-codes the id.

Firefox add-on ids only need to be globally unique on AMO; the email form is a convention and the @kilo.ai part doesn't need to be a real mailbox.

Chrome

No change. Chrome's extension id is derived from the Web Store upload and isn't pinned via a key in the manifest, so there's nothing to rename and nothing collides.

Safety

Firefox OAuth redirects use browser.identity.getRedirectURL(), which is built from a per-install UUID — not the gecko id — so changing the id does not affect auth flows.

Verification

• pnpm --filter kilo-extension build:firefox → generated manifest.json now shows "id":"browser-agent@kilo.ai".

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Executive Summary

Reviewed a two-file rename of the Firefox add-on id (kilo-extension@kilocode.ai -> browser-agent@kilo.ai) in wxt.config.ts and its e2e test; the change is consistent, correctly formatted, and introduces no bugs.

Files Reviewed (2 files)

• apps/extension/wxt.config.ts
• apps/extension/tests/e2e/firefox-extension.test.ts

---

_{Reviewed by claude-sonnet-5 · Input: 24 · Output: 3.1K · Cached: 438.2K}

_{Review guidance: REVIEW.md from base branch main}