I have a codebase with around 20 files, and I'm looking for the best way to share it with Claude. In the past, when I only had a few files, I could simply attach them to a chat, but now that it has grown, that process has become quite a hassle. I've seen information suggesting I can create a public repository on GitHub for Claude to access, but I keep running into issues and Claude often apologizes for misleading me. So, what's the best approach to share my source code with Claude? I also have an active Pro Plan that could be relevant.
2 Answers
You should definitely use a project setting! That’s what it’s designed for. Just make sure your files have clear names because you'll want to update them in Claude's project knowledge after making any significant changes.
You can also try using Claude Code. It lets you access and analyze your project more effectively right from the command line.
I thought Claude Code was just another name for the regular interface, but it turns out it’s a lot more functional! Too bad it comes at an extra cost.
I actually created a tool to help with this! It flattens the filenames before you copy them into project knowledge, so it's easier to differentiate between files like different package.json. It can also copy changed files into a temporary directory for easy drag and drop, and ignores binary files based on your .gitignore. Check it out here: [https://github.com/fuzz/clod](https://github.com/fuzz/clod)