Roadmap · six stages, in order
From a preview to an operating system.
VibeVM is in Developer Preview 1. This page is the order of what comes after it: six stages, each standing on the one before. It carries no dates. It is a sequence, not a schedule.
The six stages
What comes next, in this order
You are here
Developer Preview 1
What can be installed today: the vibe command, the package format, the registries it resolves packages from, and the manual on this site. The front page calls it a preview, and it is one: early, working, and not yet the whole idea.
Developer Preview 2
A more flexible and extensible core.
The second preview rebuilds the core so that more of it can be replaced or extended without touching the rest. Everything after this stage needs something from the core: a workspace that talks to it, plugins that talk to it, a marketplace that reads it, a distribution that stands on it. This is where the core learns to be built on.
Zap
A local workspace for running coding agents in parallel, announced and in development.
Zap is to put projects, agent conversations, questions, managed work and Git worktrees on one map on your own machine, with the agents you already have accounts for. It is an announcement, not a release: its own page says what it will be. On this road it is the first product to arrive after the second preview.
Its own page: Why Zap
The first community packages
The registries fill with packages other people wrote.
A package manager with one author is a build tool. With many, it is a commons. Once this stage holds, the spec you need may already exist, written by someone who met your problem before you did, and installing it is one line.
IDE plugins
For IntelliJ IDEA and Visual Studio Code.
Until this stage vibe is a terminal. After it, vibe is also a panel beside the code, in two editors a great many developers already have open. What the terminal answers today, the editor will answer in place.
A library and marketplace
A place of our own for browsing packages, in the spirit of Steam.
A registry answers a name you already know. A store front shows you what you did not know to look for. This stage gives packages the second kind of place: covers on shelves rather than names in a list, and room to browse.
Spec-Driven Linux
A Linux distribution whose package manager is vibevm.
The last stage turns the argument around. Today a spec stack is installed into a system. Here the system is what gets installed: packaged, pinned and described the way a stack is, by the same tool. The discipline stops at no boundary.
Its future home: specdrivenlinux.org
How to read this page
Six stages, in this order. No dates.
Each stage stands on the one before it, and a date written here would be a guess dressed as a promise. When a stage lands, the news channel says so, and the marker on this page moves.
From here
Where a stage landing is announced first: the Telegram channel, and the chat for questions.
Follow the news →The Big VisionWhy the road goes where it goes: the essay behind every stage on this page.
Read the essay →DocumentationStart where the marker is: the manual for what can be installed today.
Open the manual →