claude-code - 💡(How to fix) Fix [Bug] /setup-bedrock propagates shell env to all active sessions, causing mid-session model switches and session loss [2 comments, 3 participants]

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/abradley/.local/share/claude/versions/2.1.110 (expected in multi-process scenarios)\n at kU_ (/$bunfs/root/src/entrypoints/cli.js:2751:2153)\n at Mt6 (/$bunfs/root/src/entrypoints/cli.js:2751:1233)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-16T01:00:17.523Z"},{"error":"Error: Duplicate hooks file detected: ./hooks/hooks.json resolves to already-loaded file /Users/abradley/.claude/plugins/cache/everything-claude-code/everything-claude-code/1.0.0/hooks/hooks.json. The standard hooks/hooks.json is loaded automatically, so manifest.hooks should only reference additional hook files.\n at Mz9 (/$bunfs/root/src/entrypoints/cli.js:1035:6544)\n at async Pz9 (/$bunfs/root/src/entrypoints/cli.js:1035:12757)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-16T01:00:17.542Z"},{"error":"Error: Duplicate hooks file detected: ./hooks/hooks.json resolves to already-loaded file /Users/abradley/.claude/plugins/cache/everything-claude-code/everything-claude-code/1.0.0/hooks/hooks.json. The standard hooks/hooks.json is loaded automatically, so manifest.hooks should only reference additional hook files.\n at Mz9 (/$bunfs/root/src/entrypoints/cli.js:1035:6544)\n at async Pz9 (/$bunfs/root/src/entrypoints/cli.js:1035:12757)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-16T01:00:23.739Z"}]

TL;DR

Run /setup-bedrock in a fresh terminal with no other Claude Code sessions open to prevent session corruption.

Guidance

• The issue is caused by the CLAUDE_CODE_USE_BEDROCK=1 environment variable set by /setup-bedrock propagating to all child/sibling shell processes, affecting other Claude Code sessions.
• To verify the issue, check if other sessions switch to Bedrock and throw model availability errors after running /setup-bedrock in one session.
• As a temporary workaround, run /setup-bedrock in a separate terminal to isolate its effects.
• Consider reviewing the environment variable handling in the /setup-bedrock wizard to prevent unintended propagation.

Example

No code snippet is provided as the issue is related to environment variable propagation and shell process management.

Notes

The provided errors in JSON format seem unrelated to the primary issue of session corruption caused by environment variable propagation. The Duplicate hooks file detected errors may be a separate issue that requires attention.

Recommendation

Apply the workaround: run /setup-bedrock in a fresh terminal with no other Claude Code sessions open. This will prevent the environment variable from affecting other sessions until a more permanent fix is available.