gemini-cli - 💡(How to fix) Fix Fetch error while being asked whether to approve `write_file` [2 comments, 2 participants]

Debug Console (F12 to close) │ │ │ │ ℹ Error authenticating: Error: When using Gemini API, you must specify the GEMINI_API_KEY environment variable. █│ │ Update your environment and try again (no reload needed if using .env)! █│ │ at main (file:///C:/nvm4w/nvm/v24.13.0/node_modules/@google/gemini-cli/bundle/gemini.js:14947:17) █│ │ █│ │ ℹ Authenticated via "gemini-api-key". █│ │ ⚠ [STARTUP] Cannot start phase 'load_builtin_commands': phase is already active. Call end() before starting again. █│ │ ⚠ [LocalAgentExecutor] Skipping subagent tool 'brainstorm-planner' for agent 'brainstorm-planner' to prevent recursion. █│ │ ⚠ [LocalAgentExecutor] Skipping subagent tool 'cli_help' for agent 'brainstorm-planner' to prevent recursion. █│ │ ⚠ [LocalAgentExecutor] Skipping subagent tool 'codebase_investigator' for agent 'brainstorm-planner' to prevent recursion. │ │ ⚠ [LocalAgentExecutor] Skipping subagent tool 'generalist' for agent 'brainstorm-planner' to prevent recursion. │ │ ✖ [ERROR] [IDEConnectionUtils] IDE fetch failed for http://127.0.0.1:62903/mcp TypeError: fetch failed │ │ at Object.processResponse (file:///C:/nvm4w/nvm/v24.13.0/node_modules/@google/gemini-cli/bundle/chunk-ZTFHMKKJ.js:194045:20) │ │ at file:///C:/nvm4w/nvm/v24.13.0/node_modules/@google/gemini-cli/bundle/chunk-ZTFHMKKJ.js:194426:23 │ │ at node:internal/process/task_queues:149:7 │ │ at AsyncResource.runInAsyncScope (node:async_hooks:214:14) │ │ at AsyncResource.runMicrotask (node:internal/process/task_queues:146:8) { │ │ [cause]: HeadersTimeoutError: Headers Timeout Error │ │ at FastTimer.onParserTimeout [as _onTimeout] │ │ (file:///C:/nvm4w/nvm/v24.13.0/node_modules/@google/gemini-cli/bundle/chunk-ZTFHMKKJ.js:181361:33) │ │ at Timeout.onTick [as _onTimeout] │ │ (file:///C:/nvm4w/nvm/v24.13.0/node_modules/@google/gemini-cli/bundle/chunk-ZTFHMKKJ.js:174425:18) │ │ at listOnTimeout (node:internal/timers:605:17) │ │ at process.processTimers (node:internal/timers:541:7) { │ │ code: 'UND_ERR_HEADERS_TIMEOUT' │ │ } │ │ } │ │ ✖ [ERROR] [IDEClient] IDE connection error. The connection was lost unexpectedly. Please try reconnecting by running /ide enable │ │ fetch failed │ │ ⚠ Error waiting for confirmation via IDE TypeError: fetch failed █│ │ at Object.processResponse (file:///C:/nvm4w/nvm/v24.13.0/node_modules/@google/gemini-cli/bundle/chunk-ZTFHMKKJ.js:194045:20) █│ │ at file:///C:/nvm4w/nvm/v24.13.0/node_modules/@google/gemini-cli/bundle/chunk-ZTFHMKKJ.js:194426:23 █│ │ at node:internal/process/task_queues:149:7 █│ │ at AsyncResource.runInAsyncScope (node:async_hooks:214:14) █│ │ at AsyncResource.runMicrotask (node:internal/process/task_queues:146:8) { █│ │ [cause]: HeadersTimeoutError: Headers Timeout Error █│ │ at FastTimer.onParserTimeout [as _onTimeout] █│ │ (file:///C:/nvm4w/nvm/v24.13.0/node_modules/@google/gemini-cli/bundle/chunk-ZTFHMKKJ.js:181361:33) │ │ at Timeout.onTick [as _onTimeout] │ │ (file:///C:/nvm4w/nvm/v24.13.0/node_modules/@google/gemini-cli/bundle/chunk-ZTFHMKKJ.js:174425:18) │ │ at listOnTimeout (node:internal/timers:605:17) │ │ at process.processTimers (node:internal/timers:541:7) { │ │ code: 'UND_ERR_HEADERS_TIMEOUT' │ │ } │ │ } │ │ ✖ ========================================= │ │ This is an unexpected error. Please file a bug report using the /bug tool. │ │ CRITICAL: Unhandled Promise Rejection! │ │ ========================================= │ │ Reason: TypeError: fetch failed │ │ Stack trace: │ │ TypeError: fetch failed │ │ at Object.processResponse (file:///C:/nvm4w/nvm/v24.13.0/node_modules/@google/gemini-cli/bundle/chunk-ZTFHMKKJ.js:194045:20) │ │ at file:///C:/nvm4w/nvm/v24.13.0/node_modules/@google/gemini-cli/bundle/chunk-ZTFHMKKJ.js:194426:23 │ │ at node:internal/process/task_queues:149:7 │ │ at AsyncResource.runInAsyncScope (node:async_hooks:214:14) │ │ at AsyncResource.runMicrotask (node:internal/process/task_queues:146:8) │ │ ✖ [ERROR] [IDEConnectionUtils] IDE fetch failed for http://127.0.0.1:62903/mcp TypeError: fetch failed │ │ at Object.processResponse (file:///C:/nvm4w/nvm/v24.13.0/node_modules/@google/gemini-cli/bundle/chunk-ZTFHMKKJ.js:194045:20) │ │ at file:///C:/nvm4w/nvm/v24.13.0/node_modules/@google/gemini-cli/bundle/chunk-ZTFHMKKJ.js:194426:23 ▄│ │ at node:internal/process/task_queues:149:7 █│ │ at AsyncResource.runInAsyncScope (node:async_hooks:214:14) █│ │ at AsyncResource.runMicrotask (node:internal/process/task_queues:146:8) { █│ │ [cause]: HeadersTimeoutError: Headers Timeout Error █│ │ at FastTimer.onParserTimeout [as _onTimeout] █│ │ (file:///C:/nvm4w/nvm/v24.13.0/node_modules/@google/gemini-cli/bundle/chunk-ZTFHMKKJ.js:181361:33) █│ │ at Timeout.onTick [as _onTimeout] █│ │ (file:///C:/nvm4w/nvm/v24.13.0/node_modules/@google/gemini-cli/bundle/chunk-ZTFHMKKJ.js:174425:18) ▀│ │ at listOnTimeout (node:internal/timers:605:17) █│ │ at process.processTimers (node:internal/timers:541:7) { █│ │ code: 'UND_ERR_HEADERS_TIMEOUT' █│ │ } █│ │ } (x15)

TL;DR

The issue is likely caused by a timeout error when trying to fetch data from the IDE, and a potential workaround is to adjust the timeout settings or check the IDE connection.

Guidance

• Check the IDE connection settings to ensure it is properly configured and connected.
• Consider increasing the timeout value to prevent the HeadersTimeoutError from occurring.
• Verify that the GEMINI_API_KEY environment variable is set correctly, as the error message suggests it is required.
• Review the chat history and terminal output to identify any patterns or clues that may indicate the root cause of the issue.

Example

No specific code example is provided, as the issue seems to be related to configuration and connection settings rather than code.

Notes

The issue may be related to the reported terminal output jittering problem, which could be contributing to the error. However, without further information, it is difficult to determine the exact cause.

Recommendation

Apply a workaround by adjusting the timeout settings or checking the IDE connection, as the root cause of the issue is unclear and may require further investigation.