Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Contents
New here? Start with Installation, then Getting Started.
Overview
VT Code is an open-source Rust terminal coding agent for interactive and long-running autonomous work. A responsive TUI, safe tools, multi-provider LLM support, open protocols, and extensible Skills take you from question to reviewed change without leaving the terminal.
Status: Active development. Local inference and some automation flows are experimental and may change between releases.
Behind the build: Building VT Code, a year in: harness design, evals, security, and lessons from a year of building.
Why VT Code
- Harness, not a wrapper: the model reasons; the harness enforces progress with tools, sandbox, evals, and state.
- Safety-first: sandboxed shell, command policies, per-workspace approvals, and fail-closed handling of injection, path/symlink escape, and env leakage.
- Built for long runs: durable session memory, spooled output, auto-compaction, and verification before "done".
- Protocol-native: MCP, Skills, Agent Plugins, ACP (Zed), A2A, and ATIF export with no core forks.
- Parallel by design: worktree isolation, propose/verify sub-agents,
/planworkflow, and cost guardrails. - Runs anywhere: 30 providers plus local Ollama, LM Studio, and llama.cpp.
Quick start
|
# or: brew install vinhnx/tap/vtcode | cargo install vtcode
# or `vtcode login` for OAuth providers
See Installation and
Getting Started. Never commit API keys
or put them in vtcode.toml.
WebMCP browser bridge (opt-in)
Pair a running session from the TUI (/webmcp pair <origin>) or serve a
bounded workspace (vtcode webmcp serve --origin <origin> --allowed-root <dir>).
Hosted app: https://vtcode.vinhnx.chatgpt.site/ · fallback:
https://vinhnx.github.io/VTCode/. Details: user guide,
deployment reference.
Documentation
- Start: Installation · Getting started · Wiki · Blog: Building VT Code, a year in
- Use: TUI · CLI · WebMCP · Automation · Planning · Configuration
- Extend: Skills · Plugins · MCP · Editors
- Operate: Safety · Protocols · Loop engineering · Architecture
Providers
30 built-in providers, custom OpenAI-compatible endpoints, and local backends. Provider Guides is the source of truth for credentials and model defaults.
Restrict providers per workspace with providers_whitelist in vtcode.toml.
Local inference (experimental) via Ollama, LM Studio, and llama.cpp, managed
with /local in the TUI: see Local Models.
Development
Rust stable, edition 2024. ~30 crates layered as
types → config → core → tools → agent → TUI, with ThreadEvent as the
authoritative runtime contract. See Development setup
and Testing.
Contributing
VT Code grows with its community. Bug fixes, docs, ideas, testing, and reviews are all welcome.
Ways to contribute
- Security advisories: Please report vulnerabilities privately first: Security Policy.
- Bug fixes and patches: Small or large, every fix counts.
- Documentation: Guides, examples, and corrections help everyone.
- Features and ideas: Open an issue or start a discussion.
- Code reviews and testing: Trying things out and reporting breakage keeps the project healthy.
Getting started
- Browse good first issues
- Read CONTRIBUTING.md for humans
- Check AGENTS.md for AI agents
Small, focused PRs merge fastest. If you get stuck, open an issue for help.
Contributors
Thank you to everyone who shaped VT Code.
Support
Sponsorship
VT Code is built and maintained in spare time. If it helped you ship or learn something, a sponsorship keeps the project independent.
License
First-party code is MIT OR Apache-2.0. See LICENSE. Third-party code keeps its original licenses: see THIRD-PARTY-NOTICES.