You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Two new activation events are available for extensions:
462
+
463
+
* `onTerminal`: Triggered when any terminal is opened.
464
+
* `onTerminalShellIntegration`: Triggered when rich shell integration is activated for a terminal.
465
+
466
+
You can specify a `shellType` to target specific shells. For example, `onTerminalShellIntegration:bash` activates when shell integration is enabled for a Bash terminal.
459
467
460
468
## Proposed APIs
461
469
@@ -487,15 +495,6 @@ The new Chat Session Provider API proposal enables extensions to integrate their
487
495
488
496
This API is still in early stages and is likely to change. However we're already using it to power the new [GitHub coding agent session flow](#chat-sessions-experimental), which loads chats from GitHub and allows you to chat with an agent that is controlled entirely by GitHub.
489
497
490
-
### Terminal activation events
491
-
492
-
Two new activation events are available for extensions:
493
-
494
-
* `onTerminal`: Triggered when any terminal is opened.
495
-
* `onTerminalShellIntegration`: Triggered when rich shell integration is activated for a terminal.
496
-
497
-
You can specify a `shellType` to target specific shells. For example, `onTerminalShellIntegration:bash` activates when shell integration is enabled for a Bash terminal.
498
-
499
498
### Task execution terminal
500
499
501
500
Extension authors can now access the terminal associated with a running task via the new `taskExecution.terminal` property. This makes it easier to identify which terminal is linked to a specific task and interact with it programmatically.
0 commit comments