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

[Feat]: add support for --disable-extensions

Open
#6,722 2 comments 7 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript, vscode
Domain
cli, devtools, security

Research direction

No file or test is named in the issue. Start by locating code-server's command-line option handling and the path that initializes extensions; then determine how the flag should persistently disable them and add or update coverage for the option. Done means code-server accepts --disable-extensions and extensions remain disabled as requested.

Written by the indexing model from the issue text.

Description

enhancement

What is your suggestion?

  • add support for --disable-extensions to code-server

Why do you want this feature?

I work at a company that bootstraps development environments with vscode. Our customers are security conscious and have found that certain extensions contain security vulnerabilities. We want to permanently disable these extensions.

Are there any workarounds to get this functionality today?

Not that I know of

Are you interested in submitting a PR for this?

Yes

Dominant language
TypeScript
Stars
79.4k
Forks
6.9k
Avg merge
2d 13h
Merged PRs (30d)
39

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 coder/code-server

All issues in coder/code-server

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.