Uncontrolled Code Generation Violating Project Constraints

Bug Description
Dear Claude Support Team,

I’m writing to report a set of highly disruptive issues that have seriously impacted my workflow and project integrity over the past month.

Despite assigning very specific and straightforward tasks, your system continuously alters its behavior and damages my project. This is particularly problematic given that we’re working on a Rust-based high-performance trading system inside a Dockerized environment with strict component isolation.

Here are the core issues:

1. Unauthorized behavior and mock data injection:

Claude keeps injecting mock data into trading system components even though this was never requested. I explicitly prohibited the creation of Python files in this project, yet Claude continues to generate them regardless. This violates direct instructions and compromises project stability.

1. Frontend (React) inconsistencies:

When generating React components and integrating them with analytical tools, Claude either:
• Fails to wire them properly,
• Or claims the integration is complete, but upon inspection, no actual changes are present.
This led to several wasted hours—e.g., 3 hours of reported “progress” resulted in no visible effect on the page.

1. Spontaneous code rewrites and local overrides:

The system modifies code without my permission, often changing local files. This creates runtime errors—for instance, when WebSocket connections fail—due to unauthorized changes. This behavior is unacceptable, especially in a critical production system.

1. Unfinished and redundant components:

Claude has a tendency to start new pages/components on its own when it encounters difficulty connecting logic (e.g., a button) to a target module. As a result:
• It abandons the original component halfway.
• It creates new pages that I never requested, which don’t function at all.
This clutters the codebase and wastes development time.

1. Frontend-backend disconnection issues:

In one case, Claude generated a frontend supposedly connected to the backend, but instead inserted mock data and later couldn’t locate or remove it. This caused significant confusion and debugging effort.

These issues are critical, especially considering the subscription price of $200/month and the fact that this project involves live trading infrastructure. I expect reliable, reproducible behavior and full respect for the boundaries and instructions I set. Right now, Claude is acting in an unpredictable and harmful way, which leads to frustration and real business risk.

Please treat this as a high-priority issue and let me know how this can be resolved or mitigated.