Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Improve Constrained Runspace Debug Experience

Open
#2,294 0 comments 1 reaction 2 assignees View on GitHub

@JustinGrote is already working on this.

Since Jun 3, 2026.

  • #2295 by @copilot-swe-agent — open

Assessment

This issue has not been assessed yet.

Description

Area-Debugging Issue-Enhancement

If you start a debug in a constrained runspace, wait-debugger will silently be skipped and cause the debugger to skip breakpoints, leading to a confusing user experience.

If when a powershell launch config is started, we should check the runspace if constrained mode is enabled. If it is, we should check if all the powershell commands we use for DAP like get-variable, wait-debugger, get-psrunspace are available. If any are not available, we should stop the debug session and present a dialog saying "Cannot start debugging because you are running PowerShell in a constrained language mode that does not have the required debug commands available. Please contact your administrator to add the debug commands to your constrained runspace."

Dominant language
C#
Stars
767
Forks
266
Avg merge
3d 16h
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from PowerShell/PowerShellEditorServices

All issues in PowerShell/PowerShellEditorServices

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.