[Epic] Expand Platform Integration Bridges (Cursor, Grok, Perplexity, DeepSeek, Kimi)

[vinaykolupula]

Overview

As the AI ecosystem expands, ContxtAI needs to support context management and UI injections across a wider variety of web-based LLM interfaces and AI coding environments. This epic tracks the implementation of new platform bridges for highly requested interfaces.

Goals

• Identify and map the DOM structure, input areas, and response containers for each target platform.
• Implement reliable extension/contents/bridges/ logic for context injection, extraction, and UI overlay rendering (Context Thermometer, Fade Warnings).
• Ensure Local Scrubbing rules apply seamlessly across all new platforms.

Platform Integration Tracker

• Cursor ([Feature] Platform Bridge Integration: [Cursor] #3 ) - Priority: High
• Grok ([Feature] Platform Bridge Integration: [Grok] #4 ) - Priority: Medium
• Perplexity ([Feature] Platform Bridge Integration: [Perplexity] #6 ) - Priority: High
• DeepSeek ([Feature] Platform Bridge Integration: [DeepSeek] #5 ) - Priority: Medium
• Kimi ([Feature] Platform Bridge Integration: [Kimi] #7 ) - Priority: Low/Medium

General Requirements for Every Bridge

1. DOM Observation: Must reliably hook into dynamic page navigation (React/Next.js/Vue routing) without losing state.
2. Input Injection: The platform's prompt input area must seamlessly accept context payloads without triggering application errors.
3. Response Parsing: Auto-Distillation needs to correctly identify and extract generated code blocks or formatted text from the assistant's response.
4. UI Injection: The Highlight-to-Save menu and Context Thermometer must render cleanly above the platform's native z-index layers.

Note: Please check off the platforms above as their respective bridge PRs are merged.