Skip to content

Disable extensions when launching Extension Host for debugging - #1860

Merged
edelauna merged 1 commit into
Zoo-Code-Org:mainfrom
daewoongoh:vscode-launch-disable-extensions
Oct 3, 2026
Merged

edelauna merged 1 commit into
Zoo-Code-Org:mainfrom
daewoongoh:vscode-launch-disable-extensions

Conversation

@daewoongoh

Copy link
Copy Markdown
Contributor

Related GitHub Issue

Closes: #1859

Description

Added the --disable-extensions argument to the "Run Extension" configuration in .vscode/launch.json. This prevents other installed extensions from loading alongside the extension being debugged, avoiding interference during debugging.

Test Procedure

  • Launch the Extension Development Host in VS Code via F5 (Run Extension)
  • Confirm that no other installed extensions are loaded in the new window, and only the target extension is activated

Pre-Submission Checklist

  • Issue Linked: This PR is linked to an approved GitHub Issue (see "Related GitHub Issue" above).
  • Scope: My changes are focused on the linked issue (one major feature/fix per PR).
  • Self-Review: I have performed a thorough self-review of my code.
  • Testing: New and/or updated tests have been added to cover my changes (if applicable).
  • Visual Snapshot (UI changes only): N/A — no UI change.
  • Documentation Impact: I have considered if my changes require documentation updates (see "Documentation Updates" section below).
  • Contribution Guidelines: I have read and agree to the Contributor Guidelines.

Visual Snapshots

N/A — configuration-only change, no UI impact.

Videos (interaction / animation only)

N/A

Documentation Updates

  • No documentation updates are required.

Additional Notes

Small devex change to improve the local debugging environment.

Get in Touch

hehegwk_23849

Prevents other installed extensions from interfering while testing this one.
@coderabbitai

coderabbitai Bot commented Sep 29, 2026 •

Copy link
Copy Markdown
Contributor

Review in Change Stack →

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository: Zoo-Code-Org/Zoo-Code/.coderabbit.yaml

Review profile: ASSERTIVE

Plan: Advanced

Run ID: aa059bc9-38cb-457b-b483-f22cb9686010

📥 Commits

Reviewing files that changed from the base of the PR and between 778ad3e and 30f4faf.

📒 Files selected for processing (1)
  • .vscode/launch.json

Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 2 remain after this review.

📜 Recent review details
🔇 Additional comments (1)
.vscode/launch.json (1)

13-13: LGTM!


📝 Summary

Summary by CodeRabbit

  • Chores
    • Updated the extension’s development launch configuration to disable other extensions while running. This affects the development environment only; it does not change functionality for end-users.

Walkthrough

The Run Extension debug configuration now passes --disable-extensions alongside the extension development path. This change applies to the local debug launch configuration.

Changes

Extension Debug Launch

Layer / File(s) Summary
Disable other extensions during launch
.vscode/launch.json
The Run Extension launch arguments now include --disable-extensions.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Bug fix · Severity of issue fixed: Low

Merge Risk: ⚪ Minimal · up to 30f4f

F5 continues to activate Zoo Code in the Extension Development Host without loading other installed extensions. No actionable merge-blocking risk remains.

Architecture Summary

Architecture risk: 🔵 Low · up to 30f4f

The changed surface does not map to a changed system, dependency edge, entrypoint, or external dependency.

Changed systems: None identified.

Architecture concerns
No architecture-level concerns identified.

Review details

Before / after behavior

  • observed — Modified behavior in .vscode/launch.json: The launch arguments now include --disable-extensions in addition to --extensionDevelopmentPath.
🚥 Pre-merge checks | ✅ 8
✅ Passed checks (8 passed)
Check name Status Explanation
Linked Issues check ✅ Passed Issue [#1859] requires the local "Run Extension" configuration to launch the Extension Development Host without other installed extensions. .vscode/launch.json now includes "--disable-extensions" …
Out of Scope Changes check ✅ Passed The change is limited to .vscode/launch.json and the local Run Extension debug configuration. It does not change packaged extension code or end-user runtime behavior. The change stays within issue…
Regression Evidence ✅ Passed PASS. The pull request changes only .vscode/launch.json and adds --disable-extensions to the existing Run Extension launch arguments. This is a mechanical local debug configuration change, which…
Security Boundaries ✅ Passed PASS: The only changed path is .vscode/launch.json. It adds the static --disable-extensions argument to the local Run Extension launch configuration. The change does not expose secrets or PII, p…
Persistence Integrity ✅ Passed The pull request changes only .vscode/launch.json. It adds --disable-extensions to the VS Code Run Extension launch arguments. This is a local debug configuration change and introduces no persis…
Lifecycle Resource Cleanup ✅ Passed PASS: The pull request changes only .vscode/launch.json by adding the --disable-extensions argument to the Run Extension launch configuration. The changed path creates no listener, watcher, prov…
Title check ✅ Passed The title clearly and concisely describes the main change: disabling other extensions in the Extension Host during debugging.
Description check ✅ Passed The description includes the linked issue, change summary, implementation details, manual test steps, checklist, documentation assessment, and additional context. The unchecked testing item is appropr…
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create a new PR

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@github-actions

github-actions Bot commented Sep 29, 2026 •

Copy link
Copy Markdown
Contributor

Review status

Thanks for contributing. This comment tracks the review sequence and the next action.

Current step: Wait for GitHub to finish calculating mergeability.

Review-state labels are managed by this workflow; do not edit them manually. community-approved is managed the same way — do not add or remove it manually. It signals a fresh community code approval for the current head as an advisory priority only; maintainer review is still required.

@codecov

codecov Bot commented Sep 29, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@github-actions github-actions Bot added coderabbit-review-active Required CI passed; CodeRabbit review is active awaiting-coderabbit Waiting for CodeRabbit to approve the latest commit labels Sep 29, 2026
@github-actions github-actions Bot added awaiting-maintainer CodeRabbit approved; waiting for a human maintainer and removed coderabbit-review-active Required CI passed; CodeRabbit review is active awaiting-coderabbit Waiting for CodeRabbit to approve the latest commit labels Sep 29, 2026

@edelauna edelauna 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.

Thanks! Makes sense.

@edelauna
edelauna added this pull request to the merge queue Oct 3, 2026
Merged via the queue into Zoo-Code-Org:main with commit 7214352 Oct 3, 2026
18 of 19 checks passed
@daewoongoh
daewoongoh deleted the vscode-launch-disable-extensions branch October 13, 2026 00:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

awaiting-maintainer CodeRabbit approved; waiting for a human maintainer

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[ENHANCEMENT] Disable other extensions when launching the Extension Development Host for debugging

2 participants