Carrier OS Agent for VS Code

Carrier OS Agent brings AI-powered coding assistance directly into VS Code. Describe a bug or feature request in plain language, and the agent investigates your repository, prepares an implementation plan, and presents proposed changes as native VS Code diffs.

You stay in control: the default Manual mode asks before each proposed file change and command. Other permission modes can pre-authorize some operations; higher-risk commands still require approval. If tests fail, the agent analyses the result and may propose corrective changes; the selected permission mode controls whether those changes need approval.

Highlights

Investigate a project with repository-aware file reads and search.
Review a structured plan before changes are proposed.
Review proposed changes in VS Code's native diff editor; the permission mode determines whether an approval prompt is required.
Choose how the agent handles file changes and commands with the permission mode; Manual presents separate approval prompts.
See test output, failure analysis and proposed corrections in the same task.
Use your Carrier OS account, available models and plan.

Requirements

VS Code: Version 1.90 or later.
AI area: Requires VS Code 1.106 or later. Earlier versions can open Carrier OS from the Activity Bar.
Carrier OS account: Required to sign in and use the plan, credits and models available to your account.
Optional command execution: Requires local command execution to be enabled in the cos CLI and a configured runtime. Enter /settings commands on in the cos CLI shell; /settings in the extension panel opens VS Code settings.
- macOS/Linux: Docker Engine.
- Windows: Bundled Job Object helper. Native Windows runtime acceptance is still in progress.

Without a configured runtime, the agent can still investigate, plan and apply approved file changes.

Getting started

Open a repository folder in VS Code.
Open Carrier OS from the AI area (VS Code 1.106+) or click its icon in the Activity Bar on the left.

Both open the same agent and conversation.
Sign in with Carrier OS — your browser opens the Carrier OS website to approve this device. It is your existing Carrier OS account: the same one you use on the website and with the cos CLI, with the same plan, credits and model access.
The first time you work in a folder, Carrier OS asks whether it may work there. (This is the same trust setting the cos CLI uses.)
Type a task, for example: “Fix the cart total bug — the subtotal ignores quantity. Find the root cause, fix it, and run the relevant tests.”

What you see

Step	In VS Code
Investigation	Each file read and search, as it happens
Plan	Task, files, validation command, risk
Change	A native diff in the editor; an Apply / Reject prompt when required by the permission mode
Test	When a command needs approval, a Run / Reject prompt names it, its runtime and network; then the panel shows the result
Failure	The failing test with expected/received values, the analysis, then a corrective diff subject to the permission mode
Done	Files changed, validation results, operation IDs

Type the next task straight away; the agent keeps the context of earlier work in the same conversation (and re-reads files before changing them).

Approvals and security

Permission modes control approvals. Manual (the default) asks before each file change and command. Accept Edits allows file changes without an individual prompt. Auto also allows contained low-risk commands without a prompt; commands that write files or install packages still ask. Plan disables file changes and command execution.
In Manual mode, file-change approval and command approval are separate. Approving a file change never approves a command.
Approvals happen in VS Code's own dialogs — chat content cannot draw or answer them. An approval is never restored after a reload or restart.
In an untrusted workspace Carrier OS can read and explain code but never changes files or runs commands.
Commands run only when local command execution is enabled and the selected permission mode allows them. Manual prompts for approval; Auto can run eligible low-risk commands without a prompt. On macOS/Linux, commands run inside an isolated Linux container with network access disabled. On Windows, the bundled Job Object helper manages command execution; native Windows runtime acceptance is still in progress.
The extension is an interface, not a second agent: the Carrier OS backend reasons; the bundled Carrier OS CLI engine reads, diffs, writes, runs and enforces every boundary; your account, plan and credits are decided by the backend.

Commands

From the Command Palette: Carrier OS: Open Agent · New Task · Cancel Task · Explain This Code · New Conversation · Sign In · Sign Out · Switch Account · Open Settings

In the panel, type / to see commands grouped by purpose:

Task and chat: /plan, /permissions, /mode, /switch, /stop.
Code help: /explain, /review, /fix, /test, /search, /security-review.
Context and changes: /context, /changes, /undo, /rewind, /compact, /clear, /memory, /init.
Account and models: /usage (also /cost and /credits), /model, /fast, /hipwr, /switch-account (also /login), /history (also /resume), /settings (also /config), /release-notes, /export, /help.

Settings

Setting	Default
`carrieros.enableFileChanges`	`true`	Permit proposed file changes. The permission mode controls whether changes need an individual prompt; trusted-workspace and safety checks still apply.
`carrieros.enableCommands`	`true`	Permit agent-proposed local commands subject to the selected permission mode and safety checks. This setting can only restrict execution; commands also require the separate `cos` CLI opt-in (`/settings commands on` in the CLI shell) and a configured runtime.
`carrieros.execution.dockerSocket`	—	Docker Engine socket for the isolated macOS/Linux runtime; used only when `COS_COMMAND_DOCKER_SOCKET` is not set
`carrieros.execution.image`	—	Pinned Docker runtime image (`sha256:…`), used only when `COS_COMMAND_IMAGE` is not set
`carrieros.voice.ffmpegPath`	—	ffmpeg for voice input; found on PATH when empty

Signing out

Carrier OS: Sign Out revokes this device's session and signs out the cos CLI on this computer too — they share one session.

Privacy

Your task prompt, editor context and repository file contents needed for the task are sent to Carrier OS services. Relevant content is sent on to the selected model provider to generate a response. Approved command output can also be returned for analysis. The service records activity and operation metadata; tool results are temporarily stored to support delivery and recovery. Sign-in uses the shared Carrier OS CLI device session on this computer.

For information about data handling, review the Carrier OS Privacy Policy and Terms of Service.

Troubleshooting

Sign-in does not start (DEVICE_START_FAILED): check your connection and try a new sign-in request. Approve the newest code promptly. If it keeps failing, ask your Carrier OS administrator to confirm the server has the CLI device sign-in routes deployed, then contact support.
The agent cannot work in the folder: open the project folder in VS Code and grant workspace trust when prompted. Untrusted workspaces are read-only.
Tests or commands are unavailable: enable commands in both places—the extension's carrieros.enableCommands setting and /settings commands on in the cos CLI shell—and configure the platform's runtime. In Manual mode each command needs its own approval; Auto mode can run eligible contained commands without a prompt.
Need diagnostic details: open View → Output and select Carrier OS. Remove personal paths or other sensitive information before sharing logs.

Support

Homepage · Support · Source code · Changelog · License · support@carrieros.ai

Carrier OS Agent

Carrier Os