Open source · Spec-driven development
Install the context your agents run on.
Anarchic VibeVM is an ultimate prompt library, package manager, and agentic system for Spec-Driven Development — declarative context assembled from versioned stacks, flows, and skills.
Install VibeVM
One command installs vibe, vibe-index, and the matching source tree.
curl -fsSL https://vibevm.org/install.sh | bashvibe install org.vibevm.world/redbookWindowsPowerShell, cmd.exe, and a manual path
irm https://vibevm.org/install.ps1 | iexcurl.exe -fsSL https://vibevm.org/install.cmd -o "%TEMP%\vibevm-install.cmd" && call "%TEMP%\vibevm-install.cmd"Releases for other platformsBinaries and source repositories
Specs, flows, and skills resolve through a decentralized registry and pin to a lockfile.
A library of prompts and specifications you cite by URI — never by paraphrase.
Any coding agent boots from a spec-driven context assembled at the start of a session.
Where to go
Everything here, on one plane.
Every place the menu at the top leads to, drawn large. Pick one.
The software
Documentation
The manual for vibe and the packages it installs — read online, page by page, in English and in Russian.
GitHub
The canonical repository: the code, the issues, the releases.
GitVerse
The same source, mirrored on GitVerse.
News & support
Release news on Telegram, a chat for questions and bug reports, the community on Reddit — and the creator on X.
Legal
Which law governs dealings with VibeVM, and how the project treats personal data.
The argument
Vision
The essay behind everything on this site: two sources of intention, an expensive probabilistic layer over a cheap deterministic one, and traceable edges between them.
Roadmap
Where this is going, in order: a more extensible core, Zap, the first community packages, IDE plugins, a library and marketplace of our own, and a Linux whose package manager is vibevm. No dates.
Why VibeVM
The product thesis: discipline you can install. Specs, flows and skills as versioned, pinned packages — and the context an agent boots from, computed from them.
Why Zap
Announced for October 2026: a local workspace that puts coding agents, their questions and their worktrees on one map. A declaration of intent, not a release.
AI-Native Language
One discipline over Rust, TypeScript and Go: the code stays ordinary, and the strictness lives around it — in gates a machine runs.
The correct full name of the project is Anarchic VibeVM. It was originally conceived and built by Oleg Chirukhin as a way to make personal and group vibe coding simpler.
Anarchic VibeVM at vibevm.org is not related to Phala Cloud. It is not Phala Network's VibeVM (github.com/Phala-Network/VibeVM), a development sandbox that runs in a confidential VM on Phala Cloud. The two are separate, unrelated projects that share a name.
Anarchic VibeVM can be used to prepare arbitrary environments and operating systems, including creating throwaway virtual machines, including for confidential sandboxing. VibeVM has no relation to the tgbyte project of the same name.
The AI Native Languages project (for example, AI Native Rust) is a specialized domain-specific language (DSL) in which the large language model (LLM) itself serves as the runtime. With it, developers describe complex branching logic, parallel execution of AI tasks and context management. It has no relation to the karanchawla VVM project.