Key Facts
- ✓ Hover is a Chrome extension that provides IDE-style hover tooltips on any webpage.
- ✓ It detects code blocks, sends tokens to an LLM (via OpenRouter or custom endpoints), and caches the documentation.
- ✓ The extension uses Chrome's permission system to ensure granular control over where it runs.
- ✓ Custom endpoints allow integration with AWS Bedrock, Google AI Studio, or company-specific infrastructure.
- ✓ It is built with TypeScript, Vite, and Chrome extension APIs.
Quick Summary
A new tool named Hover aims to bridge the gap between local coding environments and the open web by bringing IDE-style documentation directly to browsers. Developed as a Chrome extension, Hover allows users to see instant, detailed tooltips for code snippets found on documentation sites, ChatGPT, Claude, and other web platforms. The tool leverages Large Language Models (LLMs) to generate this documentation dynamically, mimicking the experience of using a sophisticated code editor like VS Code or IntelliJ.
The core functionality relies on a seamless background process. When a code block enters the user's viewport, the extension identifies specific tokens and sends them to an LLM provider. Users can choose between OpenRouter or a custom endpoint. Once the LLM generates the necessary documentation, the data is cached. This ensures that when the user hovers over the code, the documentation appears instantly without needing to re-process the data. The extension is built using TypeScript, Vite, and standard Chrome extension APIs, signaling a robust and modern technical foundation. It is currently pending release on the Chrome Web Store.
How Hover Works
The mechanism behind Hover is designed to be efficient and non-intrusive. The extension does not process every piece of text on a webpage; instead, it activates specifically when a code block comes into view. This targeted approach minimizes resource usage and ensures that the tool only engages when necessary. The workflow follows a distinct three-step process designed to balance speed with accuracy.
First, the extension detects tokens within the visible code block. Second, these tokens are sent to an LLM via a connection to OpenRouter or a user-defined custom endpoint. The LLM analyzes the code and generates documentation relevant to the specific tokens identified. Third, this generated documentation is stored in a cache. When the user eventually hovers their cursor over the code, the cached documentation is retrieved and displayed immediately. This architecture ensures that the user experience remains snappy, avoiding the latency often associated with real-time API calls.
Privacy and Enterprise Integration
Privacy and security were central design goals during the development of Hover. The extension utilizes Chrome's granular permission system. This means the tool does not have access to every website the user visits by default. Instead, users must explicitly grant permission for Hover to run on specific domains. This granular control prevents the tool from operating on sensitive pages where code documentation might not be needed or desired.
Furthermore, Hover addresses the needs of corporate environments through support for custom endpoints. For companies with existing infrastructure, the extension allows users to bypass third-party services entirely. Users can point the extension directly to their own internal systems, such as AWS Bedrock or Google AI Studio. This feature ensures that proprietary code never leaves the company's secure perimeter, making the tool viable for enterprise adoption.
Technical Stack and Availability
The extension is built with a modern technology stack, utilizing TypeScript for type safety and maintainability, and Vite for fast builds. It relies on the standard Chrome extension APIs to interact with the browser. The developer has announced that Hover is coming to the Chrome Web Store soon. They have also expressed a desire for community feedback, specifically regarding the onboarding experience and general user experience (UX), acknowledging that several design decisions were made during the development process.




