In-place explanations
Select code, a flag, or a shell command and read the explanation right next to the page content. No tab switching, no copied prompts, no extra workflow.
Chrome extension
Explain code and commands without leaving the page.
Highlight a snippet, right-click, and get a layered answer that covers the fragment itself, the parent concept, examples, and common mistakes. It is built for readers who spend all day inside the browser.
example.dev / docs / select-to-explain
12
git checkout -b feature/refactor
13
git push origin feature/refactor
14
git status --short
Right click any selection
Summaries stay in Markdown
Selection aware
Explains the fragment and the larger concept behind it.
Page mode
Summarizes a whole article or docs page when you right-click the page.
Provider choice
Works with Gemini or OpenRouter so you can use the stack you already trust.
Features
Built for reading docs, code reviews, and command-line snippets.
The extension is opinionated about teaching: it stays close to the text you selected, but it does not stop at the raw fragment. It gives the context a reader actually needs.
Whole-page summaries
Right-click a page and ask for a concise summary of the entire article. Useful for long docs, RFCs, changelogs, and codebase notes.
Configurable providers
Choose Gemini or OpenRouter, set your model, and keep prompt templates editable from the settings page. The extension stays flexible without becoming complicated.
Chrome-native polish
The UI follows browser language settings, stores preferences in Chrome storage, and behaves like an extension, not a separate product shell.
How it works
Three steps from selection to explanation.
The flow is deliberately short. You do not need to open a separate website or manage a second interface just to ask a question.
-
01
Highlight the thing you do not understand.
It can be a command, a method call, a flag, or a small code fragment.
-
02
Right-click and choose the explanation action.
The floating panel appears near the selection and starts streaming a response.
-
03
Read the summary, background, examples, and notes.
The answer is formatted for scanning, so the important part shows up first.
Install
Try it locally in under a minute.
If you are not loading it from the Chrome Web Store yet, the extension can be installed as an unpacked directory during development.
Go to chrome://extensions and enable Developer mode.
Choose the repository root after running pnpm build.
Open the settings page and enter your API key and model choice.
Privacy
Built to keep the extension on the user’s side of the browser.
Preferences are stored locally in Chrome storage. Requests go only to the provider the user selected, and the public website is static.
Does the site talk to the extension?
No. The website is a separate public page used to explain the extension and its setup.
Can I change the prompt style?
Yes. The settings page exposes the prompt templates so the explanation style can be tuned.
What models are supported?
Gemini and OpenRouter are the supported providers in this repository.
Ready to use
Read code in context, not in a separate tab.
The extension is designed to fit into the way you already browse docs and code. Install it locally, point it at your provider, and start explaining snippets in place.