Grok Bot cloud computer unresponsive since Oct 21 after 4 rebuilds – hoping for a file-preserving fix (ticket T-I8769)

Hi @Colin, thanks for getting back to me so quickly.

I also came across your updated workaround in this thread:

Would replacing both .bashrc and .profile with the clean defaults from /etc/skel/ be a better and simpler approach in my case, rather than downloading and manually editing the problematic lines?

My main concern is preserving the existing environment, including our bots’ workflows, configurations, files, and backups. Could replacing those two files disrupt any existing routines or services, even if the underlying files and data remain intact?

Also, would a targeted server-side repair of those files under ticket T-I8769 be possible, without involving my personal Mac?

I’d appreciate your recommendation on the safest approach for my existing setup. Thanks!