You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I launch the gemini-cli from my terminal, there is a significant delay of approximately 8 to 12 seconds before the tool becomes responsive and ready for use. This happens every time I start the application.
OS: [ x64 Windows 11, version 24H2]
Terminal: [cmd]
gemini-cli version: [v0.1.13]
2025-07-20.182430.mp4
What did you expect to happen?
I expected the command-line interface to launch almost instantly, or at least with a much shorter delay (e.g., under 2 seconds). A quick startup is typical for most CLI tools and would lead to a more fluid and efficient user experience.
Client information
Details
$ gemini /about
# paste output here
Proposed solution
Proposed feature to solve this:
Stop MCP server init from blocking startup but continue to have it block submission of first prompt sent to Gemini CLI that talks to the model.
Do not have MCP server init block tool calls to recognized tools. Tool calls to unknown tools should ideally wait until the MCP servers are initialized so the full list of MCP tools is known.
When we are waiting after submitting a prompt due to slow MCP server startup, the status message should show "Waiting for MCP servers to load..." rather than a clever phrase.
Do not block UI startup reading folders at startup. Same as for MCP, reading folders should not block typing in the input prompt but the first input prompt should not get sent to the model until all folders are read.
Running the /mcp command should show the current status of mcp server loading if MCP servers are being initialized. Ideally it would show as a dialog that updated as the MCP servers loaded but it would be acceptable if it just showed the current state and surfaced a message in the chat once all tools loaded.
What happened?
When I launch the gemini-cli from my terminal, there is a significant delay of approximately 8 to 12 seconds before the tool becomes responsive and ready for use. This happens every time I start the application.
OS: [ x64 Windows 11, version 24H2]
Terminal: [cmd]
gemini-cli version: [v0.1.13]
2025-07-20.182430.mp4
What did you expect to happen?
I expected the command-line interface to launch almost instantly, or at least with a much shorter delay (e.g., under 2 seconds). A quick startup is typical for most CLI tools and would lead to a more fluid and efficient user experience.
Client information
Details
Proposed solution
Proposed feature to solve this:
Stop MCP server init from blocking startup but continue to have it block submission of first prompt sent to Gemini CLI that talks to the model.
Do not have MCP server init block tool calls to recognized tools. Tool calls to unknown tools should ideally wait until the MCP servers are initialized so the full list of MCP tools is known.
When we are waiting after submitting a prompt due to slow MCP server startup, the status message should show "Waiting for MCP servers to load..." rather than a clever phrase.
Do not block UI startup reading folders at startup. Same as for MCP, reading folders should not block typing in the input prompt but the first input prompt should not get sent to the model until all folders are read.
Running the
/mcpcommand should show the current status of mcp server loading if MCP servers are being initialized. Ideally it would show as a dialog that updated as the MCP servers loaded but it would be acceptable if it just showed the current state and surfaced a message in the chat once all tools loaded.