Explain the code GitHub Copilot wrote
Unvibe is a free desktop app for Mac and Windows that explains the code you select in plain English. A suggestion that looks right is easy to accept with one Tab. Select the code GitHub Copilot wrote, press Control+U (Ctrl+Alt+U on Windows), and Vibe explains it in a panel beside your editor, at the depth you pick.
Download freeNo account and no API key to start.

A worked example
Say you type the comment on the first line and Copilot suggests the rest. This function is a sample written by hand for this page, the kind of code a completion offers for that comment. It is not a recorded Copilot suggestion. Every result below was checked by running it in Python 3.14:
# Parse "1h30m", "45s" or "2h" into seconds.
def parse_duration(text: str) -> int:
units = {"h": 3600, "m": 60, "s": 1}
total = 0
number = ""
for ch in text.strip().lower():
if ch.isdigit():
number += ch
elif ch in units:
total += int(number) * units[ch]
number = ""
else:
raise ValueError(f"unexpected character {ch!r} in {text!r}")
return totalThe notes below are written by hand to show what a careful read finds. They are not output from Unvibe.
- It does what the comment asks:
"1h30m"gives 5400,"45s"gives 45 and"2h"gives 7200. Because of.lower(),"1H30M"works too. - Digits are only added when a unit letter follows them, and nothing adds what is left after the loop. So
"90"returns 0 and"1h30"returns 3600, not 5400, with no error. An empty string also returns 0. "500ms"fails withinvalid literal for int() with base 10: ''. Themis read as minutes, then thesfinds no digits before it. The message points atint(), not at the input, so it is hard to trace back."1h 30m"and"1.5h"raiseValueErrorwith “unexpected character”. That may be what you want, but the comment does not say.strip()only removes spaces at the two ends.
The function is right for the three examples in its own comment. The inputs the comment does not mention, a bare number or a number at the end, come back wrong without an error. Reading it is how you find those before someone types “90”. Start with the lines you would not have written yourself: here, the end of the loop and the else.
Doing it with Unvibe
- Select the function in VS Code once you have accepted the suggestion, or the output of
git diffin Terminal. Unvibe works in any app where you can select code; in VS Code, the editor bridge (Unvibe's Settings, Integrations) adds ⌘U (Ctrl+U on Windows). - Press Control+U on a Mac or Ctrl+Alt+U on Windows. The panel opens beside your editor and the explanation streams in as it is written.
- Pick a depth. New, Beginner, Intermediate and Advanced are free; Expert is part of Pro. Switch any time and the same code is explained again at that depth.
- Type a follow-up under the explanation, such as “Why does "90" return 0 instead of 90?” The answer stays about the code you selected.
- Press Test me. It writes a question about this exact code, and up to three if you want more. Miss one and the lesson is saved to revisit later.
You can ask Copilot Chat to explain the same code: select it and type /explain, which GitHub's Copilot Chat cheat sheet describes as explaining how the code in your active editor works. Often that is enough. The difference is what happens next: a chat answer scrolls away, while Unvibe's explanation sits beside the code at the depth you chose, is saved to your Library, and Test me can check that you got it. It also works on code you select outside your editor: a git diff in Terminal, a file on GitHub, a snippet in the docs.
When Copilot's agent mode changes many files at once, Briefs list what changed in your working tree, staged files, the latest commit or a branch. Briefs are made on your computer for free; the AI explanation of a change is Pro.
Yes. AI can be wrong even when it sounds sure. Each explanation sits next to the code it describes so you can check it, and Test me helps you spot what doesn't add up.
What leaves your computer
The code you select is sent to a cloud model to write the explanation. Only what you ask about: the selected code and its language, the file's path inside your project when Unvibe knows which file it came from (like src/lib/retry.ts), and the name of the project folder you last worked in with Unvibe. With Pro, some nearby code is added for context, and Briefs send the git changes you ask the AI to explain. Any question you type is sent too. Unvibe checks the code for keys and tokens on your computer first, and from version 0.1.44 your questions and Ask Vibe chat messages too. A known key stops the request. Your repo is never uploaded. If you add your own API key in Settings, the app sends the request straight to that provider instead.
Free and Pro
Free. 50 explanations in your first 30 days without signing in, then 50 explanations a month when you sign in. No card and no separate API key.
- Explain code you select in any app
- New, Beginner, Intermediate and Advanced depths
- Follow-ups and Test me
- Lessons saved to your Library
- Briefs of your Git changes, made on your computer
- “Why does this exist?” from your Git history
- Your code checked for keys and tokens on your device
Pro, $9 a month or $81 a year. One developer account. Your Free plan keeps working until then.
- Everything in Free
- Expert depth
- AI explanations of Git diffs and change Briefs
- Answers that use nearby files
- 200 AI explanations a month
Explain the next thing Copilot writes
Unvibe is a free app for Mac and Windows. There is nothing to paste: select code in VS Code or any other app and press Control+U (Ctrl+Alt+U on Windows).
Download freeNo account and no API key to start.