DevAgent provides an inline "Fix with DevAgent" quick action that sends a small, repo-aware context payload to a local agent (backend) and returns a safe, previewable fix (diff + explanation + confidence).
This README covers quick start steps for development, how to run the backend, how to open the extension in the Extension Development Host, and tips for packaging safely.
Quick start
Open a file in the Dev Host that triggers the sample diagnostic (the project scaffold currently flags the literal TODO_ERROR).
Use the Quick Fix (lightbulb) or the command palette:
Quick Fix: hover or place the caret near the diagnostic and accept "Fix with DevAgent".
Command palette: run DevAgent: Show Fix (convenience fallback that attempts a fix for the active editor).
Status bar: the extension shows a small status item DevAgent: Ready — click it to run the fallback command.
When you trigger a fix the extension will:
Send a small, repo-aware payload to the backend.
Open a side-by-side diff preview showing the agent's explanation and the proposed file changes.
Let you confirm and apply the changes (applies only the changed hunks in the file).
Troubleshooting
No quick fix shown: make sure the backend is running and the file contains the scaffold diagnostic marker TODO_ERROR (temporary). Also rebuild and run the extension in the Dev Host (F5).
Backend errors or timeouts: check backend logs in the terminal where you started apps/backend and adjust OPENAI_TIMEOUT_MS / OPENAI_MAX_ATTEMPTS if your LLM provider is slow.
Packaging errors from vsce: use the staging script above to create a safe packaging directory.
Contributing
Project layout: apps/ contains vscode-extension and backend. Shared code lives under packages/.
If you add new diagnostics or change the activation events, update apps/vscode-extension/package.json.
