Type
Feature request
Summary
When running multiple Copilot agent sessions across multiple VS Code windows, it is easy to lose track of which session is still running, which one needs user input, and which one has finished.
Please add optional OS notifications for Copilot agent session state changes, with click-through behavior that focuses the correct VS Code window and reveals the exact chat/session.
Current behavior
Today, if I start agent work in several VS Code windows while multitasking, I have to manually remember where each session is running and periodically check each window/session.
The Agent Sessions / Sessions view helps when I am already looking at it, but I do not get an OS-level notification when a session needs attention or completes.
Requested behavior
Add an opt-in notification setting for Copilot agent sessions, for example:
- Notify when an agent session needs user input.
- Notify when an agent session finishes successfully.
- Notify when an agent session fails or is blocked.
- Clicking the notification focuses the correct VS Code window and opens/reveals the exact Copilot chat/session.
It would be useful if the notification text included enough context to identify the session, such as workspace/repository name and session title.
Why this matters
Agent mode is most useful when I can delegate work and continue with other tasks. Without notifications, I often forget which VS Code window contains the active agent session, or I discover much later that the agent was waiting for input.
This becomes especially painful when working across several repositories and worktrees at once.
Possible implementation direction
This seems like it would fit naturally on top of the existing Agent Sessions / Sessions model:
- Treat session state changes as notification triggers.
- Add user settings for which state changes should notify.
- Add notification actions such as
Open Session, Dismiss, and optionally Disable Notifications.
- Use the existing session/window routing to focus the right window and reveal the relevant session.
Similar issues searched
I searched for similar issues before filing, using terms such as:
Copilot agent session notificationagent sessions notificationcopilot desktop notificationcopilot agent finishedcopilot needs attentionCopilot chat notificationCopilot open chat session
I did not find a direct duplicate. Nearby but not equivalent issues included session visualization/session attribution and terminal cleanup requests.
Environment
- VS Code: 1.120.0
- GitHub Copilot Chat: 0.48.1
- OS: Linux
Type
Feature request
Summary
When running multiple Copilot agent sessions across multiple VS Code windows, it is easy to lose track of which session is still running, which one needs user input, and which one has finished.
Please add optional OS notifications for Copilot agent session state changes, with click-through behavior that focuses the correct VS Code window and reveals the exact chat/session.
Current behavior
Today, if I start agent work in several VS Code windows while multitasking, I have to manually remember where each session is running and periodically check each window/session.
The Agent Sessions / Sessions view helps when I am already looking at it, but I do not get an OS-level notification when a session needs attention or completes.
Requested behavior
Add an opt-in notification setting for Copilot agent sessions, for example:
It would be useful if the notification text included enough context to identify the session, such as workspace/repository name and session title.
Why this matters
Agent mode is most useful when I can delegate work and continue with other tasks. Without notifications, I often forget which VS Code window contains the active agent session, or I discover much later that the agent was waiting for input.
This becomes especially painful when working across several repositories and worktrees at once.
Possible implementation direction
This seems like it would fit naturally on top of the existing Agent Sessions / Sessions model:
Open Session,Dismiss, and optionallyDisable Notifications.Similar issues searched
I searched for similar issues before filing, using terms such as:
Copilot agent session notificationagent sessions notificationcopilot desktop notificationcopilot agent finishedcopilot needs attentionCopilot chat notificationCopilot open chat sessionI did not find a direct duplicate. Nearby but not equivalent issues included session visualization/session attribution and terminal cleanup requests.
Environment