Hey Gemma, congrats on getting a couple launched. Yes, Claude Code has this built in and you have a few options depending on how much rope you want to give it. Press Shift and Tab together while it is running and it cycles the permission mode. One of those modes auto accepts file edits, which kills most of the prompting on its own. The tidier fix is the /permissions command. Run it and add allow rules for the tools and commands you keep approving, and it stops asking for those specifically. Put those rules in your project settings file and they persist, so the next build starts already trusted and you are not re-approving the same things every session. There is also a flag that skips permission checks entirely and lets it run completely unattended. It does exactly what you are asking for, but it means anything it decides to run, runs, with nothing standing in the way. Only worth it inside a container or a throwaway environment, never on your main machine against a live project. Start with the Shift Tab mode and the allow rules, that gets most people to the point where they can walk away and come back to something testable.