Verzeta™ for VS Code

Chat with the agents on your Verzeta Studio host from inside VS Code.

verzeta.com · X / Twitter · Reddit

Verzeta for VS Code connects VS Code to Verzeta Studio, a multi-agent AI workspace that runs on your own desktop. You chat with one agent at a time, or with a team of agents in a project room (@Coord, @Researcher, @Writer, @Critic, or any team you define). With your permission, agents can read and edit files in your workspace and run commands in it. Each agent uses the provider and model you set for it on the desktop. The extension connects only to hosts you pair it with. There is no Verzeta cloud, no telemetry, and the extension never calls a model provider itself.

Verzeta has two clients: this extension and Verzeta for Android. Both connect to the same Verzeta Studio host.

Requirements

This extension is a client and does nothing on its own. You need:

• VS Code 1.95 or newer. Showing Verzeta in the Secondary Side Bar needs VS Code 1.106 or newer; on older versions Verzeta is in the Activity Bar only.
• Verzeta Studio installed and running on a computer you control, with Remote Access turned on. See verzeta.com.
• A network path from VS Code to that computer: the same local network, or the host reachable over the internet with TLS turned on.

Without a paired, connected host, the Home tab shows only a card that asks you to add a host. There is no offline mode.

Install

In the Extensions view, search for Verzeta, or run:

code --install-extension verzeta.verzeta

Pair with your host

1. In Verzeta Studio on the desktop, open Settings > Remote Access and click Manage Remote Access. Turn on the server switch so it reads Server is running. Note one of the addresses listed under CLIENTS CAN REACH THIS HOST AT, for example ws://192.168.1.42:9180/ws. Then click Generate pair code.
2. In VS Code, run Verzeta: Add Host, or click ＋ Add host on the Verzeta Home tab.
3. Enter a name for the host and the address from step 1.
4. If the address starts with wss://, you are asked for a TLS pin. Paste the SHA-256 FINGERPRINT shown in the desktop dialog. The prompt is optional, but the desktop's self-signed certificate only works with it.
5. Enter the 6-digit pair code. A code works once and expires after 5 minutes.
6. The extension pairs and connects. The Home tab shows the host as CONNECTED, and its conversations appear in the Chat tab.

See Install and pair for details and Troubleshooting if pairing fails.

What you can do

Chat with agents

• Project rooms and group chats. Talk to several agents in one conversation. Each reply shows which agent wrote it.
• Address agents directly. Start a message with @alias to send it to one member (@Researcher find the prior art), or with @everyone to send it to every member.
• Per-agent provider and model. Each agent can use a different provider and model. You set that up on the desktop.
• Streaming and reasoning. Replies stream in as they are generated. For models that think before answering, the reasoning is shown in a collapsed Reasoning section above the reply.
• All your conversations. Direct chats, group chats and project rooms from the paired host are listed in the Chat tab.

Project rooms

The Project Rooms card on the Home tab opens your rooms and a set of templates. Click New project, or Quick Start on a template, to set the name, scenario, goal and team, including each member's provider, model and tools. When the room is created, Verzeta offers to start a group chat with the team or a 1:1 chat with each member. See Projects and rooms.

Where the chat can live

• Activity Bar. Click the Verzeta icon to open the chat in the side bar.
• Secondary Side Bar. On VS Code 1.106 and newer, Verzeta can also sit in the Secondary Side Bar. Both places show the same view.
• Editor tab. Run Verzeta: Open Chat in Editor, or click the icon in the view's title bar, to open the chat in an editor tab you can split or move.

Editor AI actions

Select code, then open the lightbulb menu (or right-click and choose Verzeta) to send the code to an agent. Each action writes a prompt from your selection and sends it to the open conversation. The agent answers in the chat, and it can edit files directly when your workspace is shared with the chat.

• Explain, Fix bugs, Refactor, Add tests and Add docs on the selected code.
• Fix this problem appears on code with an error or warning underline. It sends the diagnostic message and the code.
• Ask an Agent About This… lets you pick a group member (or @everyone) and an action, then sends the selection.
• CodeLens links (Explain, Add tests, Refactor) above functions and classes. They are off by default; turn on verzeta.codeLens.enabled to show them.

Adding context

• Send Selection to Chat and Attach Active File to Chat from the editor's right-click menu.
• Add Context (files from this workspace) or Add Files (files from your computer) from the composer's + menu.
• Drag files from the Explorer or your file manager onto the composer.
• Paste an image into the composer to attach it.
• Add Git Diff to Chat from the Source Control title bar.

In Verzeta, @ addresses agents. To add files or images, use the + menu, drag and drop, or paste.

Source control and terminal helpers

• Generate Commit Message sends your staged diff (or the working-tree diff if nothing is staged) to an agent and asks for a commit message. The reply appears in the chat.
• Send Last Terminal Command to Chat sends the last command you ran in the integrated terminal, with its output, to the chat. It needs terminal shell integration.

Canvas and applying edits

• Open canvas in editor (in the chat header's ⋯ menu) opens the conversation's canvas in a read-only editor tab. The tab updates when the agent changes the canvas.
• An Apply button appears on code blocks that name a file. It shows the change as a diff and applies it as a normal VS Code edit you can undo.

Share your workspace with a chat

Sharing your workspace (a workspace mount) lets the agents in a chat list, read and write files in your VS Code workspace. The host asks for files over the paired connection when an agent needs them. Your editor serves each file, and the host does not keep a copy. File contents an agent reads are sent to the model provider that agent uses.

• Share the workspace from the Share workspace banner in the chat, or with Verzeta: Register Workspace Mount. In a project room with one workspace folder open, it is shared automatically on your first message (turn off with verzeta.workspaceMount.autoRegister). A status bar item shows the active share.
• Permission tiers control how writes are approved:
  • Ask. Every write waits for you to approve it.
  • Smart. Edits to listed source and text file types apply without asking. Large edits (over 500 changed lines, over 256 KiB, or a new file over 200 lines) ask first. You can change the file types and the line and size limits with the verzeta.workspaceMount.smartMode.* settings.
  • Bypass. Writes apply without asking. It cannot be the default tier; you choose it each time from the tier picker.
• Safety rules apply in every tier. A write is refused when the file's extension is not on the Smart Mode list, when the path matches your blocklist, or when the content looks dangerous (for example embedded credentials, or a download piped into a shell).
• Built-in blocklist. Agents can never read or write credentials, keys, .env files, .git, node_modules or build output folders. Globs you add to verzeta.workspaceMount.blocklist block matching paths too, and verzeta.workspaceMount.allowlist can limit agents to the paths you list.

Running commands in your workspace

When your workspace is shared with a chat, an agent can run shell commands in it, such as a search, a build or the test suite. You control this for each conversation in Chat settings (the gear in the chat header), under Command execution:

• Off (the default). The command runs on the host instead. A banner in the chat offers Ask each time or Allow for this device.
• Ask. Each command waits for you to click Run or Cancel.
• Allow. Commands run without asking.

On Linux, commands run inside bubblewrap (bwrap), and on macOS inside sandbox-exec, when those are available. Windows has no sandbox, so commands there run with your full permissions. The extension warns you once per session when a command runs without a sandbox. A safety filter blocks dangerous commands in every mode, including Allow.

Privacy

• No Verzeta cloud. The extension connects only to hosts you pair it with.
• No direct model calls. The extension never talks to OpenAI, Anthropic, Gemini, Ollama or any other model provider. Your host does.
• No telemetry, analytics or crash reporting.
• Your workspace stays on your machine. Shared files are served on request and are not stored on the host.

VS Code extension  ──WebSocket──►  Verzeta Studio (your desktop)
                                        │
                                        ▼
                              Model providers you configured
                       (Ollama / OpenAI / Anthropic / Gemini / …)

Commands

Commands in the Command Palette, all under the Verzeta category:

Verzeta: Pair… and Verzeta: New Conversation also appear in the Command Palette, but they only show a message. Pair a host with Verzeta: Add Host, and start a chat with New chat in the Chat tab.

Add to Verzeta Chat is in the Explorer's right-click menu. The editor AI actions (Explain, Fix bugs, Refactor, Add tests, Add docs, Fix this problem) appear in the lightbulb menu and as CodeLens links, not in the Command Palette.

Settings

Settings for a single conversation (model, system prompt, sampling, thinking, memory, command execution and more) are in Chat settings inside the chat, not in VS Code settings, because they belong to the conversation on the host.

Security

The extension has one runtime dependency, undici, which is bundled in. The package ships two bundled scripts, dist/extension.js and dist/webview/index.js, and no node_modules folder. Pairing tokens are stored only in VS Code SecretStorage, which uses your operating system's keychain. When you enter a SHA-256 fingerprint for a wss:// host, the extension pins the host's certificate to it. See SECURITY.md for details.

Documentation

User guides are in docs/User/.

Community

• Website: verzeta.com
• X / Twitter: @VerzetaAI
• Reddit: r/Verzeta
• Verzeta Studio (desktop host): verzeta.com
• Verzeta for Android: github.com/Verzeta/Verzeta-Android

Contributing

See CONTRIBUTING.md. By contributing you accept the Contributor License Agreement.

License

Licensed under LGPL-3.0-or-later. See LICENSE and LICENSES/LGPL-3.0-or-later.txt.