Get started with Vibe Code Web
Vibe Code Web is the control plane for remote coding agents. Start a coding task from the web, supervise the agent as it works, and review the branch or pull request it produces.
Same engine under the hood as the Vibe CLI, but running in a managed cloud sandbox you reach from any browser.
Vibe Code Web is rolling out progressively across all plans. See Limits and lifecycle for quotas, model behavior, and session limits.
What you can do
With Vibe Code Web you can:
- Create projects from one or more GitHub repositories under the same GitHub owner.
- Start remote coding sessions from the web.
- Send a prompt to a cloud session from the Vibe CLI, or teleport an active CLI session to the web.
- Run agents in managed cloud sandboxes.
- Produce GitHub branches and pull requests.
- Review final code in GitHub.
It fits tasks that:
- Run remotely without local files, services, or secrets.
- Take long enough that you don't want to keep your machine open.
- End with a branch or pull request for review.
Prefer the CLI or VS Code extension when the task depends on local files, local secrets, unsupported runtimes, or direct access to your machine.
Core concepts
Vibe Code Web organizes work around three entities: projects, repositories, and sessions. A project pins one or more GitHub repositories from the same owner, and each session is one run of the agent against that project.
A project is a scoped workspace, listed in the Vibe Code Web sidebar. It includes one or more GitHub repositories from the same GitHub owner (user or organization). Sessions you run from the project share that repository scope.
At launch, project setup is limited to selecting one or more repositories from the same GitHub owner and giving the project a name.
See Projects for creation, edits, deletion, and session management.
Quickstart
You can start a Vibe Code Web session from the web or from the Vibe CLI.
- Open Vibe Code Web from the Code tab in Vibe.
- Create a project and connect one or more GitHub repositories from the same owner. See Projects.
- Click New session and enter a focused prompt. Name the file, failing test, stack trace, or expected behavior when you can.
- Watch the agent clone the repository, inspect the code, and run commands.
- Open the resulting branch or pull request in GitHub for review and merge.
Start with a small, well-scoped task. Mention the file, function, or failing test when you know it.