Autonomous Coding Agent · Multi-Provider Coding Agent

Bytos is an
Autonomous Coding Agent

An open-source, multi-provider coding agent that plans, executes and verifies software work with approval-first controls. Currently available as a VS Code extension.

Current platform: VS Code. Open source · Apache-2.0 · provider keys in SecretStorage. See how it works Available on the Marketplace

Auto Phase plan settings in Bytos inside Visual Studio Code
Install in under a minute

Download Bytos

Bytos runs inside Visual Studio Code. Install it from the Visual Studio Marketplace, add your own model key, and start in under a minute.

Windows, macOS and Linux. No Bytos account required. Get VS Code first.

Multi-provider

One agent, multiple model providers

Choose the provider and model that fit the task, or give each Auto Phase its own settings.

Provider choice

OpenRouter, Anthropic, OpenAI, Google Gemini, AWS Bedrock, Azure, GCP Vertex, Cerebras, Groq and OpenAI-compatible endpoints.

Per-task and per-phase models

Use different providers or models for planning, implementation, review or each sequential Auto Phase.

Local models and key control

Connect Ollama or LM Studio, and keep provider keys in VS Code SecretStorage instead of plaintext files.

Built for real coding work

Three things Bytos does differently from a chat window.

Plan first, then execute

Bytos breaks a task into steps, shows the plan and checks in before risky actions. Every change is a reviewable diff.

Approval-first tools

File reads, edits, terminal commands, browser access and MCP tools require your approval until you opt in per category.

Bring your own key

Connect OpenRouter, Anthropic, OpenAI, Gemini, local Ollama and more. Keys stay in VS Code SecretStorage.

Security and privacy defaults

Bytos is designed to stay local-first and approval-first.

Fail-closed approvals

File reads, edits, terminal commands, browser access, MCP tools and unknown tools require approval by default. Auto-approval is opt-in per category.

Workspace boundaries

File tools enforce a canonical workspace boundary, including absolute paths, traversal, Windows drive/UNC paths and symlinks.

Telemetry off by default

Telemetry is enabled only by an explicit opt-in. Disabling it stops PostHog events and feature flags.

Community & launches

Find Bytos Across the Developer Community

Discover Bytos, follow development updates, explore the source code, and join the community.