Opportunity (captured from a real scenario)
2026-05-30: Wanted to enable the coauthor plugin by default in the manuscript-irrelevant project by editing its .claude/settings.json. This is exactly the cross-scope settings promotion claude-scope is meant to handle — but doesn't do yet. Logging the concrete use case rather than blocking on it (edit was made by hand).
Use case
- Take a setting (here: enable plugin
coauthor) and apply/promote it into a target project's .claude/settings.json scope via the GUI, instead of hand-editing the JSON.
- Generalizes to: promote any individual setting between scopes (user ↔ project ↔ local) and toggle plugin enablement per project.
Approach
TBD — feeds the broader scope-promotion model. Filed as a backlog opportunity, not a committed spec.
Acceptance criteria
Opportunity (captured from a real scenario)
2026-05-30: Wanted to enable the
coauthorplugin by default in themanuscript-irrelevantproject by editing its.claude/settings.json. This is exactly the cross-scope settings promotion claude-scope is meant to handle — but doesn't do yet. Logging the concrete use case rather than blocking on it (edit was made by hand).Use case
coauthor) and apply/promote it into a target project's.claude/settings.jsonscope via the GUI, instead of hand-editing the JSON.Approach
TBD — feeds the broader scope-promotion model. Filed as a backlog opportunity, not a committed spec.
Acceptance criteria