Skip to content
| Marketplace
Sign in
Visual Studio Code>Other>Vecto CoderNew to Visual Studio Code? Get it now.
Vecto Coder

Vecto Coder

Developeraman

| (0) | Free
Vecto Coder is a provider-neutral coding agent for VS Code. (stable release channel)
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Vecto Coder

A coding assistant that works in your editor and keeps you in control of changes.

Vecto Coder helps you understand and update your project using your selected AI provider. Review file changes in the editor, choose whether to keep or revert them, and approve terminal commands before they run.

What you can do

  • Ask questions about your project and get help making code changes.
  • Work with OpenAI, Anthropic, Google Gemini, Ollama, and compatible providers.
  • Review tracked edits and revert them from your editor.
  • Use your own provider credentials.
  • Consult your personal coding guidance, agents, and skills stored in ~/.vecto.
  • Approve terminal commands individually in the chat.

Requirements

  • A VS Code compatible editor with the extension APIs Vecto Coder uses.
  • An account or local service for a supported AI provider.

Search for Vecto Coder in your editor's Extensions view, or install it from a terminal:

code --install-extension developeraman.vecto-coder

Get started

  1. Open a project folder and start Vecto Coder from the Activity Bar.
  2. Choose Vecto Coder: Set API Key, select your provider and credential slot, and enter your key. Vecto Coder saves it in the editor's secure credential storage and loads available models.
  3. Select a model and describe the task. Review proposed file changes in the editor; approve terminal commands in the chat when needed.

On first startup, Vecto Coder creates a user configuration folder at ~/.vecto and an empty .env template if they do not exist. To use portable environment credentials, add a variable to ~/.vecto/.env and reference it from your provider configuration. Never place real keys in project files or share them publicly.

Privacy and safety

Your provider credentials are stored locally by the editor or in your user-level .env file. Workspace content needed to answer a request is sent to the provider you selected. File changes are tracked for review, and terminal commands require your approval before execution.

Read the user guide for setup and usage details, and security and privacy for data-handling information.

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft