ctxdexSynthetic model data for learning
CLICommandPlugins & marketplacesPlugin packages

ctxdex code plugin uninstall <PLUGIN>

Plugin Uninstall/code/commands/cli/plugin-uninstall

Uninstall plugins.

Options
3
Arguments
1
Examples
2
Industry
3 of 5 mapped

About

Supported options and rules: --scope user|project; --keep-data; --force.

Syntax

The canonical syntax string as recorded in the catalogue. It is authoritative — it is never reconstructed from the option and argument lists below.

ctxdex code plugin uninstall <PLUGIN>

Subcommand of ctxdex code plugin

Arguments

  • pluginidentifierRequiredposition 1

    Plugin name or identifier.

Options

Defaults, allowed values, conflicts and scope come from the catalogue; blank fields mean the catalogue records nothing, not that the constraint is absent.

  • --scope <enum>enumOptional

    Choose the scope in which the setting, registration or package state is read or written. Allowed values: user, project.

    Alloweduser, project
  • --keep-databooleanOptional

    Retain plugin-owned data when uninstalling the plugin. Default: False.

    Defaultfalse
  • --forcebooleanOptional

    Skip the normal confirmation or graceful safeguard where policy permits. Default: False.

    Defaultfalse

Examples

  • With options

    WITH OPTIONS
    ctxdex code plugin uninstall ui-toolkit --keep-data

    Uninstall plugins.

  • Representative options

    WITH OPTIONS
    ctxdex code plugin uninstall ui-toolkit --keep-data --scope project

    Shows representative optional controls available for this command.

Availability & requirements

Nothing recorded — this command is offered in the default session, with no repository, authentication, capability or platform requirement attached to it.

Relationships

Aliases

None recordedNo alias resolves to this command

Alternate surfaces

Not applicableThis command exists on one surface only

Related commands

None recordedNo related command is recorded

Industry comparison

3 of 5 products mapped

Command-level mappings against 5 audited products, each with its documentation source and capture date. No documented equivalent means the audit found nothing in that product’s official documentation — it is not a claim that the product lacks the capability.

Every canonical command was reviewed against all 5 products in one pass captured 2026-09-18. A product with no mapping is a reviewed finding of no documented equivalent, not an unreviewed pair.

Captured 2026-09-18 · 238 commands × 5 products

Open in Compare →