You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
testing: read config from the config-cascade layers, not ~/.claude - part 3 of 4 #18052
Part 3 of 4 of #17999, split at intake (owner Q93). The done-when below is copied from #17999 as written.
Done when
setup.sh (check and apply) names each old file it finds and offers to copy its keys into the new location after a preview and a yes, leaving the old file in place.
Size: Small
Complexity: Medium
Uncertainty: Knowable
Flags: none
Blocked by: none
Blast radius: the testing plugin's setup.sh (check and apply modes) and whoever runs it; it only copies config keys after a preview and a yes.
Reversible: yes; revert the script change, and the old file is left in place by design.
Open questions: none
Understood: part 3 of 4 of #17999. setup.sh should name each old ~/.claude config file it finds and, after a preview and a yes, copy its keys to the config-cascade location without removing the old file. Sibling parts are #18050, #18051 and #18053; this is not a duplicate. The copy target comes from the cascade-reading work in the earlier parts, so the issue lane should check their state first.
Activity
github-actions commentedon Nov 21, 2026
Size: Small
Complexity: Medium
Uncertainty: Knowable
Flags: none
Blocked by: none
Blast radius: the testing plugin's setup.sh (check and apply modes) and whoever runs it; it only copies config keys after a preview and a yes.
Reversible: yes; revert the script change, and the old file is left in place by design.
Open questions: none
Understood: part 3 of 4 of #17999. setup.sh should name each old ~/.claude config file it finds and, after a preview and a yes, copy its keys to the config-cascade location without removing the old file. Sibling parts are #18050, #18051 and #18053; this is not a duplicate. The copy target comes from the cascade-reading work in the earlier parts, so the issue lane should check their state first.
Automated triage. A maintainer reviews it.
melodic-automation-lanes commentedon Nov 21, 2026
Not admitted to the issue lane yet: blocker #18050 is not closed by a listed human or a merge.