Systems | Development | Analytics | API | Testing

Your AI coding assistant has read the entire internet. It knows every programming language, every framework, every best practice documented in Stack Overflow answers and GitHub repositories. It can generate a REST API handler in seconds that looks perfect with clean code, proper error handling, following all the patterns. But here's what it's never seen: your production traffic. Data from a real API request. Someone filling out a form with messed up or incomplete data. AI is changing how we write and test code, but there's a fundamental gap between training data and production reality.

Claude is one of the go-to AI-native code editors for developers. Because it's a simple chatbot interface housed inside a familiar CLI, it provides a pretty smooth path between traditional IDEs and agentic AI. But what's actually happening behind the scenes when you ask it to write code, generate a test, or debug an issue? Who and what is it talking to behind the scenes? Can I prevent data leakage or do I need to add another layer to my tin foil hat? To answer these questions, I used proxymock to inspect the network traffic flowing from the Claude IDE.