Hi @katinker - this sounds like more of the same --- something isn't configured appropriately in your environment. The conda team put out a warning bulletin over macos catalina: Anaconda | How to Restore Anaconda after Update to MacOS Catalina . Please note, the conda team is now explicitly recommending the opposite of what @ebolyen suggested above: don't use their pkg installer, instead, use the sh installer.
As a general note, I have heard many anecdotal reports online regarding catalina breaking all kinda of things --- many software vendors are outright not supporting it. Perhaps you can save yourself some heartache and downgrade to the prior macos, and wait out the storm? I realize that is probably easier said than done.
Question - when you installed Catalina, did you do a clean sweep (delete and install), or did you perform an "upgrade" from the old macos? I have never seen the upgrade option work quite right, it is possible that there are shell/env issues there.
One bit of info that would help is if you run the env command (assuming this works at all):
env
If you get a "command not found" error again, maybe try:
bash
env