Hi @rxqd thanks for your thoughtful feedback! It’s incredibly helpful! 
This isn’t a definitive answer from the team, but just my personal observation:
Why codecrafters wants to install to root and asks for my password? (I’m not sure I trust it in that current stage)
You can inspect the content of the CLI installation script, or use an AI tool to analyze it.
The script contains this step:
sudo -k mv "$TEMP_FOLDER/codecrafters" "$INSTALL_PATH"
It requires your password to move the CLI binary to /usr/local/bin
, making it accessible from anywhere in your terminal.
An alternative would be to install the CLI in a non-root directory, but that would require users to manually update their PATH
.
Why my run script is named “your_program.sh” instead of just “run.sh” (it’s so toxic and unfriendly behaviour).
your_program.sh
represents the software you’re building in a challenge. For example, in the Redis challenge, it’s a placeholder for your_redis
.
Naming it run.sh
can be technically incorrect, for languages that require compilation, since it would need to both compile and run your program.
If you check the .codecrafters
folder in your repo, you’ll find two scripts:
your_program.sh
is designed to encapsulate both.
Naming is everything for every business and you’ve just failed.
We’re always open to alternative suggestions! 
I assume you’ve focused on expirienced devs wanting to learn new language and skills and wants big money cost for wat?
We strive to make CodeCrafters accessible to a wide range of developers, including beginners. If it feels otherwise, that’s something we’d love to improve.
I’m not sure I wanna pay you after all that behaviour
Hopefully, we can continue improving the platform to better meet your expectations in the future. Thanks again for your feedback!