Furstration with M1 Mac Terminal - ls, mkdir almost all commands gets killed.

If you are using third-party enhancements to your Zsh shell, including overly fancy coloration and layout, that may be the source of the problem. This has burned people before. Try a Zsh startup file without them and see if there is a difference.

I haven't had any issues with the Zsh shell in Mojave, Catalina, Big Sur, and now Monterey 12.2.1. My PATH statement is in a ~/.zshrc file, and everything works reliably.

I have been on 12.2.1 since yesterday afternoon, and I live inside a terminal emulator. I have had zero problems.

Have you granted your terminal emulator Full Disk Access ???

System Preferences -> Security & Privacy -> Privacy (tab) -> Full Disk Access -> [+] add your terminal emulator

This is the first time that I have heard of this.

A few things you could try:

1) Start in Safe Mode. Try Terminal. Same thing?

2) If the answer to the above is yes:

try changing the login shell to bash in Terminal->Preferences:

Close all Terminal windows, quit and restart Terminal. Same thing?

Please run Etrecheck and post its full report here. Use the "additional text" button and paste the report into the text box.

You need to give us more details so we can help.

What exactly do you mean they are "killed"? Say you type

ls

on the Terminal. What specifically happens?

You may also run Etrecheck and post its report here so we can look for issues.

Unusual problems often come down to specific stuff installed on a machine, and without such a report we have no idea what may be causing this.

Did you use a package manager and install the recently released Zsh 5.8.1 which has not been regression tested by Apple for currently released operating systems, or are you using a macOS beta?

What about a different shell, like tcsh? Does that work (it is in /bin/tcsh)

This has nothing to do with the update, or anything related to the system.

The only time I have ever seen anything like this is when trying to run some unsigned executable. The most likely explanation is some kind of "ports" project like homebrew.

Writing an effective Apple Support Communities question

Is this a New Issue ? If Yes, what exactly changed on this computer ?

Is this an Old Issue ? If Yes, what actions has the user taken to fix this issue ?

Reliable , accurate, details and context will really help to pinpoint a possible solution.