I've been having a frustrating experience with Claude when working on coding projects. Here's how I typically go about it: I gather my code files into one folder and provide Claude with a detailed request, answering his questions until I feel he understands around 95% of what I'm asking. Just before giving him the green light to edit my code file (which is approximately 110kb), I remind him specifically not to create new temporary files, to avoid rewriting the entire code from scratch, and just to modify the necessary parts to achieve the task at hand.
Despite all this, Claude frequently tries to create a new temp file or, at times, even overwrites my entire code, shrinking it down to just 6kb! It feels like I'm playing roulette with Claude's responses — you never know what you'll get each time. Is anyone else experiencing these issues? Could peak usage times in the U.S. be impacting Claude's performance?
4 Answers
I totally feel your pain! A single 110kb file can be a nightmare to manage. Have you thought about breaking it into smaller, focused scripts? It might help Claude understand and execute your requests more consistently.
Right! Claude seems to handle files under 1000 lines much better. But if you're not comfortable refactoring the code yourself, that could be tricky.
Can you share more details about the chat session you're having issues with? Maybe we can hop on a call or chat to brainstorm solutions together.
As a dev for Desktop Commander, I'm curious how you're handling a 110kb code file since there's a limit of 100kb. If you're hitting that, it could explain a lot. I’d be happy to help troubleshoot if you want!
What specific MCPs are you using? Those settings can really change how Claude behaves. Sometimes it's just about finding the right configuration that works for you.
Currently, I'm using Sequential Thinking, Desktop Commander, Memory, and File System. Sometimes everything works flawlessly, but other times it's a total mess. Have you found which settings work best?
Sequential thinking can be hit or miss; some say it improves results while others have turned it off for better outcomes. It’s worth experimenting with your setup.
I hear you! Refactoring sounds great, but if you're not a coder, it can feel really overwhelming. Don't stress too much about it!