Skip to main content

Auto-accepting AI edits in VS Code

When you let Copilot edit your code in agent mode, every change waits for a decision: Keep or Undo. For a small change that's fine. After ten prompts in a row, you're clicking Keep more than you're reading code.

VS Code has a setting to take that click away.

Why do we need this?

By default, edits from chat are pending until you accept or discard them. The pending state survives closing VS Code, so you can come back later and still decide.

That's a good default. But if you already review everything in a diff before you commit, the extra step per edit adds little.

Accept edits after a delay

Add this to your settings.json:

"chat.editing.autoAcceptDelay": 5

Edits are now accepted automatically after the delay. The default is 0, which means auto-accept is disabled.


You are not locked out. While the countdown runs, hover over the editor overlay controls to cancel it, and you can still Undo afterwards.


Keep approval for sensitive files

Auto-accept applies to edits after they are made. A separate setting decides which files Copilot may edit without asking you first: chat.tools.edits.autoApprove. It takes glob patterns.

This example allows everything except JSON files in .vscode and your .env files:

"chat.tools.edits.autoApprove": {
  "**/*": true,
  "**/.vscode/*.json": false,
  "**/.env": false
}

For those files you still get a diff and have to approve the edit.

Review before you commit

The VS Code docs are clear on this: if you automatically accept all edits, review the changes in source control before you commit them.

Source control also helps in the other direction. Staging your changes accepts any pending edits, and discarding them discards the pending edits too.

Tip: Newer Agent Host sessions skip the pending state entirely. The agent saves edits straight into the session's folder or an isolated Git worktree, so the diff before you commit is your only review step.

That's it! Fewer clicks, but the review step is still yours.

More information

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more

The role of ActivitySource in OpenTelemetry for .NET

While doing some pair programming to integrate OpenTelemetry tracing to a .NET application, we had a discussion on how to use the ActivitySource . It looks simple. You new one up, give it a name, start an activity, done. The discussion started when we added a second ActivitySource with the exact same name in a different class. This made us wonder: "Are we duplicating traces now? Is this a memory leak? Do we need a singleton?" So we decided to dig deeper. This post is what we learned… What ActivitySource actually is ActivitySource is part of System.Diagnostics , not part of the OpenTelemetry NuGet packages. Microsoft built tracing primitives directly into the BCL, and OpenTelemetry's .NET SDK simply listens to them. This is why you can add distributed tracing to a library without taking a dependency on OpenTelemetry at all. An ActivitySource is a factory for Activity objects, and an Activity is .NET's name for what OpenTelemetry calls a span.(don’t ask m...
Read more