microsoft / microsoft/vscode

Need to provide a reasonable way to allow the user to keep track of launched processes

Open
#336,684 0 comments 0 reactions 1 assignee Assigned to @anthonykim1 View on GitHub
Dominant language
TypeScript
Stars
193k
Forks
42.4k
PR merge metrics
PR metrics pending

Description

Version: 1.139.0-insider
Commit: https://github.com/microsoft/vscode/commit/4fa9fcf245ad90eb1f21fae5ed0511515e068b1d
Date: 2026-09-17T15:56:52Z
Electron: 43.6.0
ElectronBuildId: 15274685
Chromium: 150.0.7871.250
Node.js: 24.20.0
V8: 15.0.245.31-electron.0
@github/copilot: 1.0.84-5
@github/copilot-sdk: 1.0.13
OS: Darwin arm64 25.6.0

1. use the copilot harness
2. ask the agent to start a server process (like in https://github.com/microsoft/vscode/issues/336681 to open a resource in a browser via a web server)

-> naturally the server keeps running after the session finishes; however in yolo mode and as a side effect of running scripts I might miss that a server was started

We should have support to track launched processes, for example we could list them in a drop down in the artifacts section of the agents window similar to what we do we subagents. Need also a solution for the editor window.

Image

Contributor guide

Open the contributing guide

Research direction

Start by reading the agents window's artifacts section and the editor window experience, using issue #336681 for the server-process scenario. Define how launched processes remain visible after a session ends, including a dropdown similar to subagents and an editor-window solution. Done means users can discover and track processes started by agents or scripts.

Written by the indexing model from the issue text.

Assessment

Tech stack
electron, typescript
Domain
desktop, developer-experience
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.