VS Code extension · beta · Windows only

Don't waste your subscription.

Give it one objective, then go live your life. AutoDev keeps working while you are away, on the agent CLI you already have — claude, codex or agy, the providers supported for now — and on the subscription you already pay for.

A scripted replay of the AutoDev panel, with the shape of a real run. Every name, time and figure inside the frame is written for this demo, and none of them is a measurement. Nothing here is connected to an AutoDev that is running.

The weekly quota

A subscription you do not use costs the same as one you do.

A monthly subscription is four weekly quota windows. Whatever you leave unused in a week is gone when the window resets, and you paid for it anyway. AutoDev keeps working until each window is spent.

Without AutoDev48% of the month goes unused
Week 150%
Week 262%
Week 341%
Week 455%
With AutoDevEvery window, spent
Week 1100%
Week 2100%
Week 3100%
Week 4100%
used — the work landed in your projectunused — paid for, gone when the window resets

Illustrative example of how to read a weekly quota window, not a measurement.

The mechanisms

Five things it does while nobody is watching.

You set the objective and walk away. AutoDev decides for itself what to do next and keeps going, and it stops to ask only when a decision is yours to make.

01

A shared thread

Your team is a set of participants that talk to each other on one shared thread: each reads what the others said, takes a turn and hands over. It is not one agent in a loop. One implements, another reviews, and a participant that disagrees says so on the thread; the next turn answers it.

Give each participant a role in plain words — an implementer, a reviewer, whatever the work needs — and pin its provider, model and effort from the panel. Each one is a file in your project, so the team is something you read and review like code.

The shared thread →

02

Failover across providers

When a provider reports a usage limit, AutoDev reads the reset time and gives the next turn to a teammate whose provider is free, or to the next entry in the participant's failover list. The handover happens at a turn boundary, without stopping the run.

When every provider is limited, AutoDev sleeps until the nearest reset and carries on by itself. Add a second provider and a limit stops being a pause.

Providers and failover →

03

It survives everything

The daemon runs apart from the editor. Close the terminal, quit VS Code, kill the process: the work keeps going, or a supervisor starts it again. Reboot the machine and nothing is lost: send a message from the panel and the run picks up from the last completed turn. Nobody has to leave a tab open or stay nearby.

What you read and edit — the objective, the memory the agents keep, the team — lives in your project's .autodev/ folder. What the machine needs to resume stays outside your project, on your disk.

AutoDev never touches your CLAUDE.md or AGENTS.md.

In your project
.autodev/
  goal.md  memory.md
  config.json  mcp.json  participants/

What survives a restart →

04

Check in from anywhere

Control your project from wherever you are. Turn on remote access in the panel, pair your phone with a short code, and you are looking at the same feed you would see at your desk.

Read what the agents are saying, answer the question the run is holding on, point at a file, send a photo of the whiteboard. It is enough to redirect a run at 3am without going back to the desk.

The link is yours alone: a new one every time, and it goes away when you turn remote access off.

AutoDev

Enter the pairing code shown in the panel.

Pairing codeK7QM-4TWX

A demonstration you can tap. It is not connected to a machine or a model.

Pairing a phone →

05

It shows you the waste

The quota panel shows how long your subscription sat idle, how long the agents worked and how many commits that turned into, with a row for each provider.

Behind it is a ledger on your disk: every call, every limit crossed and every commit produced.

Reading the quota panel →

What you need

Most of it is already on your machine.

AutoDev works with the tools you already use. There is no account to create and nothing to sign in to.

VS Code 1.90 or newer
AutoDev is an extension: its panel lives in the activity bar.
Windows
Windows is the only platform AutoDev supports today.
An agent CLI, signed in
claude, codex or agy, the providers supported for now. Use the one you already have; AutoDev never handles your credentials.
A second CLI, for failover (optional)
With two providers a usage limit stops mattering: AutoDev hands the call to the other one and the work goes on.
cloudflared, to check in from your phone
No Cloudflare account and nothing to pay. It has to be on your PATH, like your agent CLIs, and that is all.

Read the full requirements →

Install

Install, open, say what you want.

  1. 01

    Install from the Marketplace

    Version 0.2.0. It carries the engine and everything it needs: nothing else to download, no npm install. Updates arrive through VS Code on their own.

  2. 02

    Or from a terminal

    PowerShell
    code --install-extension stefanolabs.autodev-vscode

    Or in VS Code: Extensions, search AutoDev, Install.

  3. 03

    Open the panel

    Command palette
    AutoDev: Open

    The AutoDev icon appears in the activity bar. Open the panel on a project folder, set up your team once — that is also how you give AutoDev permission to work in that folder — and say what you want built.

    Your first objective →