Problem Statement
Right now users have to copy-paste code into the web UI to get bug detection and suggestions. There's no way to check code directly inside the editor.
Proposed Solution
Build a simple VS Code extension that sends the currently open file's code to the existing /analyze/ API and shows the results (bugs, suggestions) as inline warnings or in a side panel.
Why it matters: Makes QyverixAI usable in a real developer's daily workflow instead of just a web demo. It's also already listed on the project roadmap.
Alternatives Considered
List other ideas if any.
Additional Context
Browser extension instead of VS Code extension — rejected because most developers using this tool are already coding in an editor, not a browser tab.
CLI tool (run qyverix analyze file.py from terminal) — could be a good future addition, but a VS Code extension gives instant, inline feedback without switching context, which is more beginner-friendly.
Keep it web-only — rejected since the roadmap already flags this as a gap, and it limits real-world adoption.
Add examples, links, or mockups if helpful.
Existing /analyze/ endpoint already returns everything needed (explanation, bugs, suggestions) in one call — the extension would just need to call it and render the response.
Similar reference: extensions like SonarLint or ESLint for VS Code show a good pattern — inline squiggly underlines for bugs + a "Problems" panel entry.
Live API docs for reference while building: https://qyverixai.onrender.com/docs
Could start minimal: right-click "Analyze with QyverixAI" on a file → opens results in a side panel. Inline squiggles can be a fast-follow.
Problem Statement
Right now users have to copy-paste code into the web UI to get bug detection and suggestions. There's no way to check code directly inside the editor.
Proposed Solution
Build a simple VS Code extension that sends the currently open file's code to the existing /analyze/ API and shows the results (bugs, suggestions) as inline warnings or in a side panel.
Why it matters: Makes QyverixAI usable in a real developer's daily workflow instead of just a web demo. It's also already listed on the project roadmap.
Alternatives Considered
List other ideas if any.
Additional Context
Browser extension instead of VS Code extension — rejected because most developers using this tool are already coding in an editor, not a browser tab.
CLI tool (run qyverix analyze file.py from terminal) — could be a good future addition, but a VS Code extension gives instant, inline feedback without switching context, which is more beginner-friendly.
Keep it web-only — rejected since the roadmap already flags this as a gap, and it limits real-world adoption.
Add examples, links, or mockups if helpful.
Existing /analyze/ endpoint already returns everything needed (explanation, bugs, suggestions) in one call — the extension would just need to call it and render the response.
Similar reference: extensions like SonarLint or ESLint for VS Code show a good pattern — inline squiggly underlines for bugs + a "Problems" panel entry.
Live API docs for reference while building: https://qyverixai.onrender.com/docs
Could start minimal: right-click "Analyze with QyverixAI" on a file → opens results in a side panel. Inline squiggles can be a fast-follow.