Setup guide
Five steps from an empty VS Code install to an agent that can inspect your project, edit files, and run commands with you approving the risky parts.
Download the local-ai-agent-0.2.0.vsix from the
download page, then run:
Windows: run it from PowerShell. Everywhere else the binary may be code, codium, or code-insiders.
Verteon runs fully local by default. Install Ollama, leave it running, then pull a model:
No API key needed for Ollama. If you would rather use a cloud model, set the provider to Groq in Settings and paste the key into the panel — it is stored in VS Code secret storage.
Click the AI Agent icon in the Activity Bar. The header shows a live provider dot: green means the health check succeeded, red means the provider is unreachable and the panel tells you why.
Open a folder first. Verteon reads and writes inside the workspace root, so an empty window is not enough.
Start with something read-only. These are safe on any project:
Watch the activity panel on the right: every tool call is reported as it starts and as it finishes.
Every command Verteon wants to run is classified into three tiers:
Safe
Read-only or standard checks. Runs without a prompt, e.g. git status, npm test.
Approval
Changes something. You approve the exact command once, e.g. npm install, git push.
Blocked
Never runs and cannot be approved, e.g. rm -rf /, curl … | sh.
Anything the classifier does not recognise defaults to approval, not to safe. Full details in the docs.
Your dashboard keeps your account details and this guide's progress together.
Go to my dashboard