What it does
Name the task, pick a length, press start. Audio and countdown begin together. When the block ends, you say in one line what landed — and that line, not a vague sense of the day, is what AI Review is built from.
Most Pomodoro extensions stop at the countdown. A countdown is the easy half. The hard half is the thirty seconds before it — deciding what this block is even for — and the thirty seconds after it, while you still remember what happened.
NEDIO asks for both, and keeps each answer short enough that you will still do it on a Friday afternoon.
A panel in the sidebar, a countdown in the status bar
The NEDIO icon in the activity bar opens a sprint panel: goal, duration, work mode, start. That is the whole surface. There is no dashboard, no task tree, and nothing to configure before your first sprint.
Once a sprint is running you can close the panel entirely. The status bar keeps the countdown and the current goal in view, which is usually all you want mid-task — 32:14 · fix auth redirect bug. Turn it off if a visible clock is its own distraction.
Work modes, because not all coding is coding
Every sprint is tagged with one of five modes: code, debug, plan, review, or deep work.
This is one tap, and it is the tap that makes the rest possible. A debugging hour and a code review hour are not the same activity, and averaging them together produces a number that describes neither. Tagging the block is what lets AI Review compare like with like later.
Set the mode you use most as your default and you will rarely touch it.
What it never reads
NEDIO reads no workspace content. Not your source, not your file names, not your repository name. There is no code analysis feature to opt out of, because there is no code analysis.
This is why the extension declares itself supported in untrusted workspaces and in virtual workspaces. Opening a stranger's repository does not change what NEDIO can see, and its server address is fixed at build time, so a folder cannot point it somewhere else.
What it does store is what you type into it: the goal of a sprint and the line you write at the end. Product telemetry is limited to events — panel opened, sprint started, an error code — never the text of a goal or a review, and it follows your editor-wide telemetry setting as well as its own.
Commands
Everything is reachable from the command palette under the NEDIO category.
NEDIO: Start Sprint
Open the panel with your defaults already filled in.
NEDIO: Connect This Editor
Link the editor to your account so sessions share one history.
NEDIO: Disconnect This Editor
Unlink this machine without touching your account.
NEDIO: Open NEDIO in Browser
Jump to the full app for AI Review and ledger.
NEDIO: Refresh Plan and Usage
Re-check your plan after upgrading.
NEDIO: Show Logs
The output channel, for when support asks.
Settings
Five settings. There is deliberately no sixth.
| Setting | Values | What it does |
|---|---|---|
nedio.defaultDuration | 15 · 25 · 45 · 60 · 90 | Duration pre-selected when the sprint panel opens. Default 25. |
nedio.defaultWorkMode | code · debug · plan · review · deepwork | Work mode pre-selected when the panel opens. Default code. |
nedio.showStatusBarTimer | on / off | Show the running sprint and countdown in the status bar. |
nedio.silenceNotifications | on / off | Enable Do Not Disturb for the length of a sprint, then restore it. |
nedio.telemetryEnabled | on / off | Product events only, and it follows the editor-wide telemetry setting. |
Browser or editor — one history either way
The extension is not a cut-down copy of the web app. It is the same account and the same session history, reached from a different place. Sprints you run in the editor and sprints you run in a browser tab land in one record.
That matters more than it sounds. The AI Review compares your sessions against each other, so a split history would mean comparing half your work to the other half and calling the difference a finding.
AI Review itself stays in the browser. An editor is a bad place to read a page of statistics, and pretending otherwise would mean building a second surface for it before the first one has earned its keep.
Frequently asked questions
Does it work in Cursor?
Yes. Cursor is built on VS Code, so the same extension installs and behaves identically. If most of your work is AI-assisted, the Cursor page covers what changes about measuring your own sessions when an agent writes part of the code.
Does NEDIO read my code?
No. The extension reads no workspace content — not file contents, not file names, not repository names. It is declared as supported in untrusted workspaces for exactly that reason: there is nothing in your folder for it to read, and its server address is fixed at build time so an untrusted folder cannot redirect it.
Do I need an account to start a sprint?
You can run the browser app with no account at all. The extension asks you to connect an editor so your sprints land in the same history as your browser sessions — otherwise AI Review would be built on half your work.
Does the music play through the editor?
Yes. Audio runs inside the extension, so there is no separate browser tab or music app to manage. Tracks are instrumental — lo-fi and ambient, no lyrics and no ads.
Will it mute my notifications?
Only if you ask it to. Turn on nedio.silenceNotifications and the extension enables the editor's Do Not Disturb mode while a sprint runs, then restores whatever the setting was before.
Can I hide the status bar timer?
Yes, with nedio.showStatusBarTimer. The sprint panel in the activity bar keeps working either way — some people want the countdown in view, others find a visible clock its own kind of distraction.
Is the extension free?
The extension itself is free, and so is everything it does in the editor: the timer, work modes, goals, the end-of-sprint review, your session log, and weekly focus statistics. The free tier includes 60 minutes of focus audio a day. Pro removes that cap and adds AI Review on the website, which reads your session history back and looks for patterns in it.