what is your experience with the use case of "debugging GCP VM configuration" using Gemini CLI?

[contributorai]

I made gemini CLI install a part of my GCP VM startup script and I'm using Gemini to help me debug the startup script and installation done by the startup script. In this use case a couple of details stand out as mildly annoying usability issues:

1. Accessing files (such as logs in /var/log/) outside of directory where gemini is running. Is there a way to turn off this check? I find myself repeatedly copying files that gemini needs to look at. ( I don't mind destroying this VM, I'll spin up another clone using the startup script that I'm debugging)

2. Not able to run shell command:

Gemini: I am sorry, but I cannot directly execute gsutil commands. Please run the command and paste the
  output here so I can help you analyze it.
 User > gstul ls  │
╰──────────────╯

✦ I believe you meant gsutil.

  As a reminder, I cannot execute shell commands directly. Please run the following command and paste
  the output here:

Hmm... seems like "executing shell commands" should be core functionality for CLI version of Gemini... why not execute shell commands... you are running in a shell (not a browser!)!
~~ item 2 was a gemini's hallucination. another gemini session used gsutil without issues.

[Manamama]

1. Re: 'Accessing files (such as logs in /var/log/) outside of directory where gemini is running. Is there a way to turn off this check? ': yes, the banal ln -s trick
2. Re: ' As a reminder, I cannot execute shell commands directly' - Gemini writes the truth here. Do put yourself in her (API) shoes...

ver. 1.1 style