fix: claude plugin install --scope local from a worktree writes the main checkout's settings.local.json #6375

Problem

Run from a linked git worktree, claude plugin install <id> --scope local (and claude plugin marketplace add --scope local) records the install in the main checkout's .claude/settings.local.json, not the worktree's. A test install meant to stay inside one worktree session therefore enables the plugin for every session in the main checkout, and the stray file outlives the worktree.

Observed

• Claude Code 2.1.289, WSL2, during Phase 7 install-and-test for PR feat(user-interface): add the user-interface plugin #6318. The user had to delete the stray .claude/settings.local.json in the main checkout by hand.
• Workaround that worked: run test installs from a throwaway non-git folder (for example under /tmp), never from a worktree.

Fix

1. Confirm whether this is intended upstream behavior (local scope keyed to the repository's main working tree) and, if not, report it upstream with /harness-ops:known-issues create.
2. Either way, state the rule where agents run local-scope test installs: plugin install-and-test from a worktree uses a non-git folder. A guardrails check that flags --scope local run inside a linked worktree would remove the need for agents to remember it.

Related

• feat(user-interface): add the user-interface plugin #6318 (where it was hit), feat(user-interface): new plugin — project-first interface guidance with terminal UI #6298.

🤖 Generated with Claude Code