Browser Extensions

Cortex Browser Extensions

Use Cortex beside web applications in Chrome, Edge, Firefox, Safari and Brave.

Cortex Browser Extensions bring conversational assistance, page context and connected enterprise work into Chrome, Microsoft Edge, Firefox, Safari and Brave. The side panel keeps Cortex beside the web application you are using, so a repository, ticket, document or cloud resource can become the starting point for a task.

Get started

Install the extension for your browser, sign in, and open the Cortex panel on a supported page. Begin with a page summary or a site-specific quick action; the usage guide covers the first conversation.

Assistance grounded in the page

The extension can use the active page and explicitly selected tabs as context. Quick actions adapt to the page: a pull request offers diff review and change summaries, a Jira ticket offers acceptance criteria, and a cloud console page offers resource explanations or configuration review. Ordinary pages provide summaries and key-point extraction.

Selected and pinned tabs also support comparisons and research workspaces. This is useful when a decision depends on several sources, such as comparing documentation with an issue and the relevant repository.

Coding and security from the browser

Repository pages can start code explanations, bug investigation, test suggestions and reviews. Security and SCA scan interfaces provide a path from code or dependency context to results. Eligible accounts also have AI Security Review and AI Threat Model workflows.

A browser conversation can prepare an investigation or review, then continue in a connected VS Code workspace or Cortex Cloud when the task needs project execution. The available handoff and tools depend on the connected workspace and enabled features.

Conversations, attachments and exports

Saved chats, collections, pinning and forks help keep long-running topics organized. In-chat search and message display controls make it easier to find the relevant response. File attachments add documents or source context, and voice input is available with microphone permission.

Export a message or conversation as PDF, Markdown, plain text or a Word document. Eligible accounts can prepare Slack or email exports. These outputs can contain the page and enterprise context used in the conversation.

Connected work and product fit

Approved MCP services bring enterprise information into the same chat, while workflow recipes support eligible multi-step work. Use an extension when you want Cortex inside your existing browser. Choose Cortex Discover for the purpose-built browser experience with native browser action and navigation controls.

Workflows for different browser tasks

Use the extension to make the current web application part of an investigation, not just to open a separate chat. Common starting points include:

A pull request: summarize the proposed change, examine the diff and ask for security or test considerations before review.
An issue or Jira ticket: clarify acceptance criteria, identify open questions and prepare an implementation objective.
Documentation or research tabs: compare sources and preserve the information relevant to a technical decision.
A cloud console: explain visible resource context and investigate a possible configuration concern with authorized service tools.
A customer or business record: combine permitted page and connector context to prepare a follow-up or engineering investigation.

These tasks use selected context and enabled tools. The extension is not an unrestricted automation interface for every page. Use Discover when the task needs its dedicated, governed browser-action capabilities.

Keep research, alternatives and execution distinct

Collections organize chats for a project or investigation. Pin a conversation you need frequently, search within a chat for a decision, or fork from a completed response to explore another approach. The original discussion remains available when the fork develops independently.

A conversation can supply the objective for an eligible workflow, but creating a collection or fork does not start an approved project change. Connected workflow views show execution progress and outstanding decisions separately from the discussion. Cortex Connect lets the objective reach a connected VS Code workspace; Cortex Cloud provides another eligible execution target.

Privacy-aware page and file context

The privacy controls distinguish quick sensitive-pattern scanning from deeper AI privacy review of chats and files. File sanitization provides another check on attachment inputs. Prompt protection helps identify instruction risk in untrusted page or repository material. Review flagged context before deciding what to send; selecting a tab does not authorize every operation in that tab’s application.

Local checks protect the pre-send boundary. They do not make remote reasoning, enterprise connector calls or Cloud tasks offline. Exports can also contain confidential page information, so choose a sharing destination appropriate for the conversation.

Mixed-browser and Apple environments

Chrome, Edge, Firefox and Brave use their respective supported extension paths. Safari uses the macOS app and Safari extension model. Its sign-in flow can complete through the Pervaziv Console and includes Apple-supported account paths. Follow the installation guide for your browser rather than installing a package intended for another ecosystem.

Organizations can provide Cortex to teams using different browsers while keeping approved enterprise connections and account access consistent. Feature availability still follows the installed version and platform.

Product background

Availability and context controls

Browser support, extension version, plan and organization policy determine which features appear. Context, saving, privacy and prompt-protection settings let you control the inputs used by the experience. Refresh page context after navigation, and review consequential operations before approving them.