gemini-cli - 💡(How to fix) Fix Subagent - Very poor performance [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
google-gemini/gemini-cli#25534Fetched 2026-04-17 08:55:34
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
Participants
Timeline (top)
labeled ×2

Code Example

> /about
CLI Version                                          0.37.1Git Commit                                           3b2d4f100                                                                                          │ 
Model                                                gemini-3-flash-preview                                                                             │ 
Sandbox                                              no sandbox                                                                                         │ 
OS                                                   linux                                                                                              │ 
Auth Method                                          Signed in with Google (ksprashanth82@gmail.com)Tier                                                 Gemini Code AssistGCP Project                                          cloudshell-gca                                                                                     │ 
IDE Client                                           Cloud Shell
RAW_BUFFERClick to expand / collapse

What happened?

The subagents are taking a very very long time to complete.

Each run (of a single thread of a single subagent) seem to be taking additively more time.

The first subagent ran in 5 mins, the second took about 12 mins, the third in sequence took over 15 mins. In fact it seems to be taking time with the status "starting...". So it is not even running for that long.

Why does a subagent take time to start? Is this a quota issue? I have a Google AI Pro plan.

<img width="1012" height="297" alt="Image" src="https://github.com/user-attachments/assets/064947af-3a1b-4f03-be80-f0a081396a9c" />

What did you expect to happen?

I expect the subagents to start immediately and process the prompt.

Client information

<details> <summary>Client Information</summary>

Run gemini to enter the interactive CLI, then run the /about command.

> /about
│ CLI Version                                          0.37.1                                                                                             │ 
│ Git Commit                                           3b2d4f100                                                                                          │ 
│ Model                                                gemini-3-flash-preview                                                                             │ 
│ Sandbox                                              no sandbox                                                                                         │ 
│ OS                                                   linux                                                                                              │ 
│ Auth Method                                          Signed in with Google ([email protected])                                                    │ 
│ Tier                                                 Gemini Code Assist                                                                                 │ 
│ GCP Project                                          cloudshell-gca                                                                                     │ 
│ IDE Client                                           Cloud Shell
</details>

Login information

gmail auth

Anything else we need to know?

No response

extent analysis

TL;DR

The subagents' increasing startup time may be related to a quota issue or resource allocation, and verifying the Google AI Pro plan's limits and usage could help identify the cause.

Guidance

  • Check the Google AI Pro plan's documentation to understand the quota limits and usage guidelines for subagents.
  • Investigate if there are any resource-intensive processes running in the background that could be affecting the subagent startup time.
  • Review the client information and login details to ensure that the authentication and authorization are correctly configured.
  • Consider reaching out to Google support to verify if there are any known issues or limitations with the Gemini Code Assist tier that could be contributing to the problem.

Notes

The provided information suggests that the issue might be related to the Google AI Pro plan or the Gemini Code Assist tier, but without more details about the quota limits and usage, it's difficult to provide a more specific solution.

Recommendation

Apply workaround: Investigate and optimize resource usage to mitigate potential quota issues, as the problem seems to be related to the increasing time it takes for subagents to start, which could be a sign of resource constraints.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING