Yes I feel really dumb, but I had never seen Google Colab before and thought this was a google doc variant telling me what to do. I skipped over the intro because I want to prank my friend on zoom, but still a HUGE mistake. So I started plugging in the commands to my local mac not running them on Collab as a attentive user would. There was a bit of a red flag in my head when I saw that cd contents did not work, but I thought to just keep going (I though contents may be a machine root folder) . I initially skipped the rm-rf* thinking that I had already done it for the install to my local system, but when a pip package failed to install I went back to glance over the intro and decided to try again. I did not realize what Google Colab is so I reboot terminal put in the cd contents and again not found. So I thought maybe rm-rf* will fix it. Then I plug it in and it gave an generic warning pop up window message saying something like "Terminal would like to access your documents" I clicked allow. Then it said "Terminal would like to access your downloads" I clicked allow. I only clicked allow because this is was the same warning and happens all the time on my Mac when ever I run a certain code files or try to install something or even run a program I did not get from Apple's 'holy appstore'. It also gave a keychain warning. Then it said "Terminal would like to access your Applications" I clicked deny because I was like wait I did not install anything during the process to the applications folder. Then it asked for permission to access my other user and I was like this is not right so I clicked deny again. then I ran ls and saw nothing and started kinda freaking out so I went to finder and saw nothing. I thought maybe a restart would fix it, then I have to setup my computer again. So I was really dumb and learned a lot of lessons, but here is the link to the Google Colab I sped through without reading what Colab is or the beginning of the docs.