Barie for VS Code

Your codebase, your machine, your models. Barie brings an agentic coding assistant into the VS Code sidebar — it reads your project, writes the code, runs the commands, and shows you every change before it lands. The intelligence runs on your own on-prem deployments, so nothing about your source leaves your infrastructure.

• Your models, on your infrastructure: Barie talks to your organisation's on-prem model deployments. Pick a deployment from the model picker, choose a reasoning level, and go — no third-party API keys, no code shipped to an outside vendor.
• Works alongside you: Barie explores the workspace on its own — lists, globs, greps, reads — then writes files and runs terminal commands with your permission. Long-running commands are left alive in the background and read back when they finish, instead of being killed at a timeout.
• Every change is reviewed in the editor: proposed edits open as a real diff. Accept or reject them chunk by chunk or file by file, straight from CodeLens actions in the gutter. Files with pending changes are marked, and Git conflicts get their own resolution flow. Nothing is written until you say so.
• A plan you can watch: Barie keeps a live task plan in the panel, so you can see what it has finished, what it is on, and what is still ahead of it on a multi-step job.
• Integrated with your workspace: attach files and images to a prompt - @-mention anything in the workspace, or use the paperclip to pick a screenshot or a log from anywhere on your machine. Barie knows the workspace it is sitting in, and skips node_modules, build output and other noise instead of drowning in it.
• Chat that survives restarts: multiple sessions, full local history, search across past conversations, and resume where you left off. Sign in once — the extension keeps the session and reconnects on its own.
• Your Barie connectors, running locally: enable a connector once in Barie — Gmail, ClickUp, HubSpot, Apollo, Slack and the rest — and its tools are available to the agent in the editor. No second config file and no second sign-in: the panel mirrors what you switched on, with a live status dot per connector and a switch per tool. The servers run on this machine, so commands, URLs, headers and tokens never leave it; each prompt carries only your connectors' names, and the agent asks for a connector's tools when it needs them.
• Agentic under the hood: subagents for parallel work, skills the agent opens when a task matches, context compaction on long sessions, and questions asked as a card in the panel when Barie genuinely needs your input.

New to Barie?

Install the extension, sign in with your Barie account, and open the Barie icon in the Activity Bar. Pick a model deployment in the composer and send your first prompt.

Requirements

• VS Code 1.74.0 or higher
• A Barie account with at least one on-prem model deployment

Connectors

Your connectors live in Barie. You connect and enable them once, on the web at Settings → Connectors on your own Barie domain — Gmail, ClickUp, HubSpot, Apollo, Slack, Google Calendar, Grafana and the rest — and the extension follows.

The plug button in the composer opens the list: a dot for whether each one is actually running, its icon, and its tools. The badge on the button is the number of tools currently available to the model. Manage opens your connector settings in the browser; Refresh asks Barie what is enabled now and brings this machine into line.

There is nothing to configure here, and no second set of credentials. A connector you switch on in Barie appears in this list and connects; one you switch off is disconnected and disappears. That reconciling happens when you open the panel, when you press Refresh, and once when the editor starts.

Where the servers actually run

On this machine. Barie hands the extension each connector's MCP server — a command to run, or a URL and a token — and the extension runs it here, next to your files. Commands, URLs, headers and tokens never leave this machine, and none of them is written to disk. Credentials are fetched fresh each time a connector is connected and live only in the extension's memory.

Each prompt carries only the names of your connected connectors — about a kilobyte. When the agent needs one, it asks for that connector's tools, and then for the one tool it is about to call. Sending them all instead cost 46,551 tokens in every model call on an account with seven connectors, and the ceiling that came with it silently dropped whichever tools came last.

Connectors that need a runtime

Most connectors are remote HTTP servers and need nothing installed. Some are local programs:

Nothing is ever downloaded on its own. A download only happens because you pressed Refresh or Retry, never when the editor starts or when the panel is opened, and it goes into the extension's own storage rather than onto your PATH.

A row that could not connect says why, on the row, and offers Retry. One connector failing never costs you the others.

Individual tools

Inside each row the tool list opens to a switch per tool, with Enable all / Disable all — a switched-off tool is never shown to the agent and cannot be called, even by name. Useful when you want a connector's 57 read tools but not its delete_task. These switches are this editor's own: they are not sent to Barie, and they survive a restart.

Commands

All Barie commands live under the Barie category in the Command Palette — pending changes, per-file accept/revert, chat sessions, history, storage location, and sign-in/sign-out. Ctrl+Shift+R (Cmd+Shift+R on macOS) opens the pending-changes review. For connectors there are two: Barie: Open Connector Settings opens your settings in the browser, and Barie: Refresh Connectors reconciles this machine with what is enabled there.

Settings

Made with ❤️ by the Barie Team