Skip to content

Allow extension-owned terminals to opt out of being a persistent terminal #118726

@Tyriar

Description

@Tyriar

Currently we enable the persistent terminal/reconnect feature if a terminal is launched by an extension, unlike the env var relaunch where we disable outright because it can cause issues with the extension as it loses access to the terminal upon relaunch.

Relaunching the PowerShell extension right now for example is a bit of a weird experience though because it creates the "PowerShell Integrated Console", and that reconnects upon reload but is no longer managed by the extension.

Before reload:

image

After reload it is restored, but no longer owned by the extension:

image

Assigning to March for exploration.

Thoughts @TylerLeonhardt @andschwa?

Metadata

Metadata

Assignees

Labels

apiapi-finalizationfeature-requestRequest for new features or functionalityinsiders-releasedPatch has been released in VS Code Insiderson-release-notesIssue/pull request mentioned in release notesterminalGeneral terminal issues that don't fall under another labelterminal-persistenceRelating to process reconnection or process reviveverification-neededVerification of issue is requestedverifiedVerification succeeded

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions