Cursorex - Chat with Cursor

Tracking since May 11, 2026.

Changelog

• May 16, 2026
  description

  Cursorex is an AI chat assistant in a persistent side panel. It connects your browsing to Cursor through a local native bridge and your Cursor API key, so answers can use real page context, tabs, files, and images—not a disconnected chat bubble.
  
  🧠 WHY IT EXISTS
  If you want an AI Chrome workflow that behaves like a research copilot instead of a generic widget, this is the shape: side panel first, multimodal attachments, and routing that knows when to read the DOM, when to use vision-style capture, and when to stay hands-off.
  
  ⚡ QUICK CAPABILITIES
  1. Chat with the active page and selected open tabs via the picker.
  2. Attach PDFs, Office files, spreadsheets, CSV, images, and text.
  3. Summarize long articles, docs, and research-style pages with structure.
  4. Run image workflows for uploads, page images, or visible captures.
  5. Choose local workspace or Cloud agents (HTTPS Git repo) once configured.
  
  💪 Bonus depth for power users:
  • Markdown with code blocks, tables, and copy-friendly controls.
  • Site-aware suggestions for common destinations (mail, notes, tasks, shopping, travel, collaboration tools, and more where adapters exist).
  
  ✅ GETTING STARTED
  1. Install Cursorex from this Chrome Web Store page, pin the extension if you like, and open the side panel from the toolbar.
  2. Install the local native bridge: see https://github.com/wideserg/cursorex-public — README and GitHub Releases (bridge bundle zip, Node.js LTS, platform installers for Windows / macOS / Linux). The installer registers Native Messaging for Chrome (and Edge where supported) so the extension can talk to the bridge.
  3. In the side panel, run Check connection and finish onboarding with a Cursor API key in Connection settings.
  4. Start with a short question about the current page, then add tabs, files, or other context as you need it.
  
  🧭 HOW IT ROUTES YOUR WORK
  🗺️ Cursorex routes across page text, hybrid reads when a site needs it, file workflows, and optional history when you opt in—so context comes from what you attach and approve, not from background guessing.
  
  Research and learning workflows that map well here:
  
  - Compare two vendor docs side by side using multi-tab context.
  - Turn a dense PDF into a same-day execution checklist.
  - Extract constraints from a spec page and validate them against your notes file.
  - Move from a news article toward primary sources with fewer duplicate tabs.
  - Keep the model anchored to what is visible and selected, not guessed from memory.
  
  🎙️ WHO THIS IS FOR
  
  🧑‍💻 High-frequency intents overlap here: AI browser assistant, side panel chat, summarize this page, summarize this video. Cursorex targets the intersection of those intents with serious context and file depth—not only developers.
  
  ➤ Strong fits:
  • Developers who already live in Cursor and want the same reasoning engine while reviewing tickets, docs, and dashboards.
  • Researchers who need PDF and arXiv-class reading support with less copy-paste friction.
  • Content operators who summarize YouTube and long web pages at volume.
  • Anyone who refuses a random third-party relay server sitting between the browser and the model account.
  
  🔐 SECURITY AND PRIVACY DEFAULTS
  
  🛡️ Security and privacy defaults are written for a cautious mindset. You connect with a Cursor API key through the local bridge; there is no separate “sign in through a hosted relay” path in this build.
  
  🔒 Microphone, history, tabs, and broad site access are requested only when a feature truly needs them. Page content, tab data, screenshots, browser history, and similar signals are used for user-requested workflows—not background profiling.
  
  🗂️ Conversation history defaults to session-only; persistent local chat history is opt-in so you decide what accumulates over time.
  
  🏗️ ARCHITECTURE IN PLAIN LANGUAGE
  
  ⚙️ Chrome Extension → Native Messaging Host → Local Bridge → Cursor (agents via local runtime)
  
  That boundary matters: it is why credentials follow a local-first pattern and why multimodal artifacts can be handled by the bridge instead of naive extension-only storage.
  
  🚀 Bottom line: if you want a Chrome side panel AI chat with a real runtime boundary, multimodal muscle, and defaults that respect privacy tradeoffs, Cursorex is built to be the bridge—not another generic sidebar clone.
  
  Built on the open-source Chromex project (https://github.com/GENEXIS-AI/chromex) with substantial changes for Cursor. Bridge releases and install docs for this distribution: https://github.com/wideserg/cursorex-public

  Cursorex is a Cursor AI browser assistant and side panel chat for Chrome. It connects your browsing to Cursor through a local native bridge and your Cursor API key, so answers can use real page context, tabs, files, and images—not a disconnected chat bubble.
  
  🧠 WHY IT EXISTS
  If you want an AI Chrome workflow that behaves like a research copilot instead of a generic widget, this is the shape: side panel first, multimodal attachments, and routing that knows when to read the DOM, when to use vision-style capture, and when to stay hands-off.
  
  ⚡ QUICK CAPABILITIES
  1. Chat with the active page and selected open tabs via the picker.
  2. Attach PDFs, Office files, spreadsheets, CSV, images, and text.
  3. Summarize this page and long docs with structured output.
  4. Run image workflows for uploads, page images, or visible captures.
  5. Choose local workspace or Cloud agents (HTTPS Git repo) once configured.
  6. Use Cursor AI chat in Chrome without switching tabs every minute.
  
  💪 Bonus depth for power users:
  • Markdown with code blocks, tables, and copy-friendly controls.
  • Site-aware suggestions for common destinations (mail, notes, tasks, shopping, travel, collaboration tools, and more where adapters exist).
  
  ✅ GETTING STARTED
  1. Install Cursorex from this Chrome Web Store page, pin the extension if you like, and open the side panel from the toolbar.
  2. Install the local native bridge: see https://github.com/wideserg/cursorex-public — README and GitHub Releases (bridge bundle zip, Node.js LTS, platform installers for Windows / macOS / Linux). The installer registers Native Messaging for Chrome (and Edge where supported) so the extension can talk to the bridge.
  3. In the side panel, run Check connection and finish onboarding with a Cursor API key in Connection settings.
  4. Start with a short question about the current page, then add tabs, files, or other context as you need it.
  
  🧭 HOW IT ROUTES YOUR WORK
  🗺️ Cursorex routes across page text, hybrid reads when a site needs it, file workflows, and optional history when you opt in—so context comes from what you attach and approve, not from background guessing.
  
  Research and learning workflows that map well here:
  
  - Compare two vendor docs side by side using multi-tab context.
  - Turn a dense PDF into a same-day execution checklist.
  - Extract constraints from a spec page and validate them against your notes file.
  - Move from a news article toward primary sources with fewer duplicate tabs.
  - Keep the model anchored to what is visible and selected, not guessed from memory.
  
  🎙️ WHO THIS IS FOR
  
  🧑‍💻 High-frequency intents overlap here: Cursor AI chat, AI browser assistant, side panel chat, summarize this page, summarize this video. Cursorex targets the intersection of those intents with serious context and file depth—not only developers.
  
  ➤ Strong fits:
  • Developers who already live in Cursor and want the same reasoning engine while reviewing tickets, docs, and dashboards.
  • Researchers who need PDF and arXiv-class reading support with less copy-paste friction.
  • Content operators who summarize YouTube and long web pages at volume.
  • Anyone who refuses a random third-party relay server sitting between the browser and the model account.
  
  🔐 SECURITY AND PRIVACY DEFAULTS
  
  🛡️ Security and privacy defaults are written for a cautious mindset. You connect with a Cursor API key through the local bridge; there is no separate “sign in through a hosted relay” path in this build.
  🔒 Microphone, history, tabs, and broad site access are requested only when a feature truly needs them. Page content, tab data, screenshots, browser history, and similar signals are used for user-requested workflows—not background profiling.
  🗂️ Conversation history defaults to session-only; persistent local chat history is opt-in so you decide what accumulates over time.
  
  🏗️ ARCHITECTURE IN PLAIN LANGUAGE
  
  ⚙️ Chrome Extension → Native Messaging Host → Local Bridge → Cursor (agents via local runtime)
  
  That boundary matters: it is why credentials follow a local-first pattern and why multimodal artifacts can be handled by the bridge instead of naive extension-only storage.
  
  🚀 Bottom line: if you want a Cursor AI Chrome extension flow with side panel AI chat, a real runtime boundary, multimodal muscle, and defaults that respect privacy tradeoffs, Cursorex is built to be the bridge—not another generic sidebar clone.
  
  Built on the open-source Chromex project (https://github.com/GENEXIS-AI/chromex) with substantial changes for Cursor. Bridge releases and install docs for this distribution: https://github.com/wideserg/cursorex-public

Permissions & access

Permissions

offscreensidePanelactiveTabtabsscriptingstoragecontextMenusnativeMessaging

Host access

<all_urls>

Screenshots