Repository navigation
feat(conventions): adopt claude plugin configure --values-stdin for plugin reconfiguration #6761
Description
Context
The plugin-reconfiguration convention and about 44 plugin READMEs ("By hand, in settings") reconfigure a plugin headlessly by rerunning claude plugin install ... --config. That rerun prints "already installed", adds an install record, and enables the plugin when the scope mismatches, and it cannot list unset options. Claude Code 2.1.285 added claude plugin configure <name@marketplace>, which lists options and which are unset, and --values-stdin, which saves a validated JSON object of single-line strings (changelog item 2.1.285-004, range v2.1.265..v2.1.296).
Problem
The new command looks like the right route, but the docs leave the details open, so the convention and READMEs cannot be switched safely.
Evidence so far
Docs check on 2026-10-10 (plugins CLI reference, plugin configure): there is no --scope flag; non-sensitive values go to user settings.json pluginConfigs per the manifest reference, which is where the convention measured --config writing. Unstated: which file configure actually writes, and whether it accepts a sensitive option. No probe has run (probed on Claude Code 2.1.296, 2026-10-10: not yet probed).
Open questions
- Which settings file does
configure --values-stdinwrite, and does it respect the plugin's install scope given there is no scope flag? - How does it handle sensitive options (keychain, rejection, or plain text)?
- Does it enable the plugin or add install records the way the
--configrerun does?
Acceptance criteria
- A recorded probe answers questions 1 to 3 on a named Claude Code version.
- The plugin-reconfiguration convention names the preferred headless route and its limits.
- The setup skills and READMEs that say "By hand, in settings" follow the convention (or a follow-up sweep issue is opened).
References
- Changelog item 2.1.285-004, https://code.claude.com/docs/en/changelog
- Related issues: Migrate per-skill .claude config files to userConfig, one conventions doc, or the cascade (ADR 0018) #5906, feat(conventions): one setup lifecycle for where plugins store team conventions and settings #6594
🤖 Generated with Claude Code
Activity
github-actions commentedon Oct 10, 2026
Proposed work class: work-class: scoped
Basis: automated intake triage; the lanes App applied this class.
Size: Medium
Complexity: Medium
Uncertainty: Knowable
Flags: none
Blocked by: none
Understood: you want the plugin-reconfiguration convention and the "By hand, in settings" READMEs to move from the
claude plugin install --configrerun toclaude plugin configure --values-stdin. First, a recorded probe has to settle three open questions. They are which settings file it writes, how it handles sensitive options, and whether it enables the plugin or adds install records. The probe settles them, so no owner decision is needed. Nothing is missing from the issue. Related issues #5906 and #6594 are already linked. I found no duplicates among the open issues.Automated triage, applied by the lanes App.
kyle-sexton commentedon Oct 13, 2026
Owner batch-ratified this admission in an attended session on 2026-10-12: work-class: scoped. Rule: class C1-C3, no trust surface, the independent check confirmed the recorded decision, and no owner step remains.
github-actions commentedon Oct 25, 2026
The triage sweep dispatched intake triage for this issue (attempt 1 of 2).