Skip to content

Add readonly and lock file commands for npm, yarn and pnpm#286612

Merged
Tyriar merged 2 commits intomainfrom
tyriar/286463
Jan 8, 2026
Merged

Add readonly and lock file commands for npm, yarn and pnpm#286612
Tyriar merged 2 commits intomainfrom
tyriar/286463

Conversation

@Tyriar
Copy link
Copy Markdown
Contributor

@Tyriar Tyriar commented Jan 8, 2026

Fixes #286463

@Tyriar Tyriar added this to the January 2026 milestone Jan 8, 2026
@Tyriar Tyriar requested a review from meganrogge January 8, 2026 20:22
@Tyriar Tyriar self-assigned this Jan 8, 2026
Copilot AI review requested due to automatic review settings January 8, 2026 20:22
@Tyriar Tyriar enabled auto-merge January 8, 2026 20:23
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds auto-approval support for read-only commands and safe lockfile-only installs for npm, yarn, and pnpm package managers to the terminal chat agent tools configuration. This allows these safe commands to be executed without explicit user approval.

Key changes:

  • Adds regex patterns for read-only commands (ls, list, outdated, info, audit, config, etc.) for npm, yarn, and pnpm
  • Adds support for safe frozen-lockfile installs (npm ci, yarn/pnpm install --frozen-lockfile)
  • Includes comprehensive comments explaining the safety of these commands

…/terminalChatAgentToolsConfiguration.ts

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
@Tyriar Tyriar merged commit dea178a into main Jan 8, 2026
22 checks passed
@Tyriar Tyriar deleted the tyriar/286463 branch January 8, 2026 21:03
@vs-code-engineering vs-code-engineering Bot locked and limited conversation to collaborators Feb 22, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Review all safe to run npm commands

3 participants