VS Code 1.137 puts your coding agent on a schedule

VS Code 1.137 shipped Automations, and the feature is exactly what the name says: your coding agent now runs on a cron. Hourly, daily, weekly, or on demand. Not a chat you start — a job that starts itself. That is a smaller feature than it sounds and a bigger operating change than it looks.

What actually happened

Per the 1.137 release notes, dated September 9, Automations "run recurring agent tasks on a schedule, so routine work does not have to be started manually." You enable chat.automations.enabled, open the Agents window, and pick Automations in the sidebar. Ship-with templates cover catching up on changes, triaging issues, and finding bugs, or you write your own prompt and schedule. It is Preview and rolling out gradually, so not every install has it yet.

Two supporting changes matter more than they read. The agent host now lets you connect to the same agent session from multiple VS Code windows — the session belongs to the host process, not to a window. And when one agent messages a busy chat via the send_message session-management tool, VS Code queues it and runs it after the active turn completes, in order. Multi-agent workflows stop racing each other.

The plumbing under all of this is the Agent Host Protocol — JSON-RPC, open spec, agent-agnostic. We flagged it in 1.135 as the part worth watching. It still is. Anyone can build a client against the VS Code CLI's agent host, or a host that VS Code connects to.

Why scheduled agents matter for your business

An interactive agent has a natural governor: you are sitting there. A scheduled agent does not. It runs Tuesday at 3am whether or not the repo is in a state worth reasoning about, and it spends tokens either way.

So price it before you schedule it. A daily triage pass across a busy repo is a real line item, and unlike a chat session nobody watches it climb. Cap it, meter it, and put the cost next to the outcome.

Then decide what it is allowed to touch. Read-and-report is the safe default — summarize changes, list stale issues, flag suspicious diffs. The moment a scheduled agent opens PRs or edits files unattended, you need branch protection, required review, and CI that would catch its worst day. The agent is not the risk. An unreviewed merge at 3am is.

The honest verdict: this is good, and it is the same feature GitHub, Warp, and everyone else shipped this year. What is portable is AHP. Build your recurring work as prompts and schedules you can move, not as configuration that only exists inside one editor.

Sources: VS Code 1.137 release notes, VS Code Agent Host docs.