Analyze, debug, and explain code directly from VS Code using the QyverixAI API.
- 🧪 Analyze (
qyverixai.analyze) — Full code analysis: explanation, bug detection, and improvement suggestions in one go. Sets inline diagnostics (squiggly lines) for detected issues. - 🐛 Debug (
qyverixai.debug) — Scan the current file for bugs, errors, and warnings. Inline diagnostics highlight problem areas in the editor. - 📖 Explain (
qyverixai.explain) — Get a plain-English summary of what the code does, its complexity, key points, and structure.
-
Open any file in VS Code.
-
Right-click in the editor and select:
- QyverixAI: Analyze Current File
- QyverixAI: Debug Current File
- QyverixAI: Explain Current File
Or use the Command Palette (
Ctrl+Shift+P) and typeQyverixAI. -
A WebView panel opens beside your editor with the results.
-
For Analyze and Debug, squiggly lines appear in the editor at the locations of detected issues. Open the Problems panel (
Ctrl+Shift+M) to see the full list.
- VS Code 1.82+
- The QyverixAI API must be running and reachable. The extension defaults to the hosted API at
https://qyverixai.onrender.com.
This extension contributes the following settings:
| Setting | Default | Description |
|---|---|---|
qyverixai.apiUrl |
https://qyverixai.onrender.com |
Base URL of the QyverixAI API |
qyverixai.timeout |
30 |
Request timeout in seconds |
- The API works best with complete, syntactically valid files.
- Very large files (>50 KB) may be truncated by the API's 50 000 character limit.
cd vscode-extension
npm install
npm run compileThe compile step emits extension.js, which matches the package entrypoint declared in package.json.
After compiling the extension:
-
Open the
vscode-extensionfolder in VS Code. -
Press F5 or navigate to Run → Start Debugging.
-
A new Extension Development Host window will open.
-
Open any source file in the new window.
-
Open the Command Palette (
Ctrl+Shift+P) and run one of:QyverixAI: Analyze Current FileQyverixAI: Debug Current FileQyverixAI: Explain Current File
The command results will appear in a WebView panel, and diagnostics will be displayed in the editor where applicable.
Breakpoints can be added by clicking in the margin next to a line number in src/extension.ts.
Useful locations include:
postToApi()– inspect outgoing API requests and responses.- Command handlers – verify command execution flow.
- Diagnostic creation logic – inspect generated warnings and errors.
- WebView rendering functions – inspect response formatting.
Place a breakpoint on the following line:
function postToApi<T>(endpoint: string, body: object, timeoutS: number): Promise<T> {Then:
- Press F5 to launch the Extension Development Host.
- Run any QyverixAI command.
- VS Code will pause execution when the breakpoint is reached.
- Inspect variables using the Debug panel.
While debugging, open:
View → Debug Console
The Debug Console displays:
- Runtime errors
- Breakpoint information
- Logged messages
- Stack traces
If a launch configuration is not automatically generated, create .vscode/launch.json:
{
"version": "0.2.0",
"configurations": [
{
"name": "Run Extension",
"type": "extensionHost",
"request": "launch",
"runtimeExecutable": "${execPath}",
"args": [
"--extensionDevelopmentPath=${workspaceFolder}"
]
}
]
}- Run all three extension commands after making changes.
- Verify diagnostics appear in the editor and Problems panel.
- Test with multiple programming languages when possible.
- Use
Ctrl+Shift+P → Developer: Reload Windowafter rebuilding. - Keep
npm run watchrunning during development for automatic recompilation.
To build an installable VSIX package:
npm install -g @vscode/vsce
vsce package
code --install-extension qyverixai-vscode-*.vsixMIT