VS Code 1.142 turns the IDE into an agent control desk: canvases, chats that move across worktrees, policies flipped on by the organization, not the developer.
The October 14 release is the second agent-focused one in a week: 1.141 (Oct 7) shipped a grid of parallel agent sessions; 1.142 gives those sessions surfaces to work on. The headline is Canvases (preview, chat.canvases.enabled): interactive surfaces alongside the chat — say, a kanban board where you move cards while the agent breaks a feature into tasks. It's an honest admission that a conversational feed cannot hold decomposition work: a twenty-task plan in a linear thread is unreadable by the second iteration. Second, chat mobility: ask in plain language and the agent moves the conversation to another folder or a fresh git worktree, history intact. Parallel sessions are the norm now, so context travels with the work instead of dying at every switch. Third, the enterprise block: admins can enforce agent sandboxing and permission policies, control the Assisted vs Allow All modes separately (permissions.disableAssistedPermissionsMode), and policy-managed chats auto-migrate to Copilot Agent Host.
The contentious thesis sits between the lines of the changelog: an engineer's focus is shifting from writing logic to orchestrating processes. The shift itself doesn't worry me — what worries me is that accountability hasn't shifted with it. Code you didn't write and don't fully understand still ships to production under your name. A control desk without review discipline is a conveyor of the unexamined: cards move, branches multiply, understanding stands still.
What this means for a team lead. Three rules. Use a canvas where the plan matters more than the dialogue — decomposition, tracking several tasks in parallel; for linear question-and-answer, chat is faster, and dragging a kanban into every ticket is cargo cult. Set a worktree convention before you have ten of them: one worktree = one task = one branch with a predictable name; orphaned worktrees get removed at the end of the day, or within a week nobody can tell which branch is alive. Flip the policies on day one: enforced sandboxing and an explicit permission mode are basic hygiene; the Magister of the Wards will have more to say about that. And one rule no setting controls: nothing merges unless a human has read it and can explain it.
📎 code.visualstudio.com/updates/v1_142