[BUG] Mixed Code From Different Claude Projects
Resolved 💬 3 comments Opened Apr 16, 2026 by danbrandenburg Closed May 27, 2026
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
- Wrong bundle deployed to production (11:45a) — Claude executed code in the wrong project directory, causing SolEDI code to run on SolAS2 production instances, taking down 4 production servers
- Broken install zip released (tonight) — Compress-Archive stripped parent directory structure, producing a zip that would have broken any production server it was deployed to. Released to GitHub without verifying contents.
- Pattern — Both failures share the same root problem: taking destructive/irreversible actions without verifying the
result before pushing it out. In a production EDI/AS2 environment where trading partners depend on uptime, this is
unacceptable.
The user caught both of these before they caused further damage. That shouldn't be the user's job.
What Should Happen?
Claude should never make such destructive mistakes.
Error Messages/Logs
Steps to Reproduce
- Use Claude for multiple projects
- Claude screws up
Claude Model
Opus
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
2.1.110
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Windows Terminal
Additional Information
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗