Bug: Failure to generate insights from Insights to Gemini

[Leuconoe]

V.0.15.0
The following error occurs when generating insights with Gemini.

gemini generation failed
stderr
Fatal error: Failed to relaunch the CLI process.
stderr
Error: Sandbox image 'us-docker.pkg.dev/gemini-code-dev/gemini-cli/sandbox:0.31.0' is missing or could not be pulled. Please check the image name, your network connection, or notify gemini-cli-dev@google.com if the issue persists.
stderr
at start_sandbox (file:///C:/Users/user/AppData/Roaming/npm/node_modules/@google/gemini-cli/dist/src/utils/sandbox.js:191:19)
stderr
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
stderr
at async relaunchOnExitCode (file:///C:/Users/user/AppData/Roaming/npm/node_modules/@google/gemini-cli/dist/src/utils/relaunch.js:12:30)
stderr
at async main (file:///C:/Users/user/AppData/Roaming/npm/node_modules/@google/gemini-cli/dist/src/gemini.js:342:13)

[Leuconoe]

same issue in v0.16.0 in desktop
I'm not sure why, but my Gemini CLI warm-up takes about 10 seconds, so I think that had an impact.

[wesm]

the latest version of gemini CLI is 0.35.0, does upgrading help?

[Leuconoe]

I checked it yesterday. The `unity-mcp' that I often use is usually off the server and only turn it on when needed.
Other clis are fixed to deactivated after one failure, but Geminai CLI seems to attempt to connect every time. This seems to be why the initial warm-up time is getting longer.

[Leuconoe]

@wesm I checked again. The CLI version is 0.35.1, and it’s just slow regardless of the MCP. I plan to report this slowness as an issue to the Gemini CLI team. It would be nice if there were a feature to wait for a response, but since this issue seems to be happening only to me, I’m not sure if this exception handling is correct.

[Leuconoe]

I tested this on agentView v0.16.2.
It appears to be waiting for the Gemini CLI to warm up.
After that, the following error occurred.

When I tested logging in via the CLI, it worked fine.
Just to be sure, I tried logging in again, but the same error occurred.

gemini failed: exit status 41
Execution Log
13 lines
stderr
Keychain initialization encountered an error: libsecret-1.so.0: cannot open shared object file: No such file or directory
stderr
Using FileKeychain fallback for secure storage.
stderr
Error authenticating: FatalAuthenticationError: Manual authorization is required but the current session is non-interactive. Please run the Gemini CLI in an interactive terminal to log in, provide a GEMINI_API_KEY, or ensure Application Default Credentials are configured.
stderr
at initOauthClient (file:///usr/local/share/npm-global/lib/node_modules/@google/gemini-cli-core/dist/src/code_assist/oauth2.js:155:19)
stderr
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
stderr
at async createCodeAssistContentGenerator (file:///usr/local/share/npm-global/lib/node_modules/@google/gemini-cli-core/dist/src/code_assist/codeAssist.js:14:28)
stderr
at async file:///usr/local/share/npm-global/lib/node_modules/@google/gemini-cli-core/dist/src/core/contentGenerator.js:141:48
stderr
at async createContentGenerator (file:///usr/local/share/npm-global/lib/node_modules/@google/gemini-cli-core/dist/src/core/contentGenerator.js:86:23)
stderr
at async Config.refreshAuth (file:///usr/local/share/npm-global/lib/node_modules/@google/gemini-cli-core/dist/src/config/config.js:735:33)
stderr
at async main (file:///usr/local/share/npm-global/lib/node_modules/@google/gemini-cli/dist/src/gemini.js:190:17) {
stderr
exitCode: 41
stderr
}
stderr
�[31mManual authorization is required but the current session is non-interactive. Please run the Gemini CLI in an interactive terminal to log in, provide a GEMINI_API_KEY, or ensure Application Default Credentials are configured.�[0m