{"version":"2.1.281","anchor":"claude-plugin-update-scope-now-defaults-to-auto-detect","canonical_anchor":"claude-plugin-update-scope-now-defaults-to-auto-detect","heading":"claude plugin update --scope now defaults to auto-detect","tier":"use","area":"Plugins","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/claude-plugin-update-scope-now-defaults-to-auto-detect","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### claude plugin update --scope now defaults to auto-detect\n\nclaude plugin update now auto-detects the scope by default instead of assuming the user scope\n\n**Unclear.** The finding does not say how auto-detect chooses a scope or what scope is used when `--cowork` is set.\n\n**What**\n\nThe `claude plugin update <plugin>` command has a `--scope` option. Its help text now says \"(default: auto-detect)\" instead of \"(default: user)\". The enable and disable commands show the same auto-detect wording.\n\nWhen you leave `--scope` out, the update command no longer fills in \"user\". The scope is left unset for Claude Code to work out, unless `--cowork` is set.\n\n**Why**\n\nIf you update a plugin without naming a scope, the command no longer assumes the user scope. That matters for a plugin that was installed somewhere else.\n\n- Area: Plugins\n- Names: `claude plugin update`, `--scope`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 1\/5"}