Skip to content

Default new cloud automations to no allowed tools - #342481

Merged
Ben Villalobos (benvillalobos) merged 2 commits into
microsoft:mainfrom
timrogers:fix/cloud-automation-default-no-tools
Oct 19, 2026
Merged

Ben Villalobos (benvillalobos) merged 2 commits into
microsoft:mainfrom
timrogers:fix/cloud-automation-default-no-tools

Conversation

@timrogers

Copy link
Copy Markdown
Contributor

New cloud automations now start with no allowed tools instead of selecting every tool in the catalog. Saving sends an explicit empty tools array without waiting for catalog loading. Editing or duplicating an automation preserves its saved tool selection, and edits with unreported tools preserve the existing configuration.

Updated dialog regression coverage for the default selection, selection labels and accessibility counts, explicit tool selection, and saving with ready, empty, loading, or unavailable tool catalogs.

No linked issue; requested as a default-behavior change.

How to test

In the Agents window, open Customizations → Automations → Create Automation, turn on Run in the cloud, and choose a repository. Verify that the tools control shows zero tools allowed and the picker starts with every tool unchecked. Create an automation without changing tools, then verify its saved tool list is empty. Explicitly select tools and confirm those selections save; edit or duplicate an existing automation and confirm its saved selections remain selected.

Validation

  • git diff --check — passed.
  • npm run build-fast -- --client-only — failed because the esbuild dependency is missing.
  • ./scripts/test.sh --run src/vs/sessions/contrib/automations/test/browser/automationDialog.test.ts --reporter dot — not run because the preceding client build failed.
  • npm run eslint -- src/vs/sessions/contrib/automations/browser/automationDialog.ts src/vs/sessions/contrib/automations/test/browser/automationDialog.test.ts — failed because the eslint dependency is missing.
  • npm run install-fast — failed with EALLOWSCRIPTS (project-scoped --allow-scripts is rejected), blocking dependency restoration.

Manual UI validation was not performed.

Preserve saved tool selections while initializing new cloud automations with an explicit empty tool list. Remove catalog-dependent default selection and update dialog regression coverage.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: dcf7492a-57a5-4314-a573-5c75a21d1c5a
Copilot AI balanced review requested due to automatic review settings October 19, 2026 05:10

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🔵 Needs a closer look

No actionable defects were identified, but regression tests and manual UI validation remain unverified.

No open issues 🎉

What changed in this PR

Changes the Agents window automation dialog so new cloud automations default to no allowed tools.

Changes:

  • Saves an explicit empty tool list without waiting for the catalog.
  • Preserves existing tool selections and unreported configurations when editing.
  • Updates regression coverage for selection labels, accessibility counts, and catalog states.
File Description
src/​vs/​sessions/​contrib/​automations/​test/​browser/​automationDialog.test.ts Updates selection expectations and tests saving across catalog states.
src/​vs/​sessions/​contrib/​automations/​browser/​automationDialog.ts Defaults new selections to empty and removes catalog-dependent saving.

Review effort: Balanced

@benvillalobos
Ben Villalobos (benvillalobos) merged commit 50d1fca into microsoft:main Oct 19, 2026
49 checks passed
@vs-code-engineering vs-code-engineering Bot added this to the 1.144.0 milestone Oct 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants