we_are_coded.by CODE · The world, decoded
БГ

Concept

Agent harness in editors

A harness is the environment where agents work inside the editor: where sessions run, who starts them, and what they see. VS Code narrows to one, JetBrains opens to many.

Updated on 13 November 2026 · Checked on 13 November 2026

The agent in your editor is not a chat. It is an environment: where sessions run, who starts them, what they see, and what is left after them. That environment is called a harness, and it is exactly what is moving at the end of 2026.

In VS Code the change is already announced. With version 1.146 on November 11, 2026, Microsoft deprecated the Local harness and removes it in February 2027. The default for new sessions since 1.143 is the Copilot harness, built on the Copilot SDK, which runs sessions through the Agent Host so they keep running in the background and open from both the editor and the Agents window. For organizations it enforces a managed sandbox and permission policies that Local does not. The setting that kept Local as the default is removed too.

In JetBrains the direction is different: not one harness, but many agents in one place. Air became generally available with the 2026.3 release on November 11, 2026. It works with Junie, Codex, Claude Agent, and GitHub Copilot and connects to other compatible agents through ACP. Each agent gets its own local Git worktree so parallel sessions do not collide. A paid JetBrains AI subscription is not required: Junie Lite is free, and AI Assistant stays as a separate plugin until early 2027.

The difference is in the philosophy. VS Code narrows to one harness that holds permissions and the sandbox. JetBrains opens the environment to outside agents and gives each its own worktree. Both answer the same problem: the agent writes fast, and the person after it reads slowly.

The visual is generated code-art, no third-party images.