-
Notifications
You must be signed in to change notification settings - Fork 216
Open
Labels
area:setupRelated to conductor:setup commandRelated to conductor:setup commandbugSomething isn't workingSomething isn't workingp1High priority. Must be fixed in the upcoming releaseHigh priority. Must be fixed in the upcoming release
Description
When running /conductor:setup to initialize the extension within gemini-cli, the process crashes with a 400 API Error. The error message explicitly states that the input token count exceeds the maximum allowed (1,048,576 tokens).
It appears the setup command attempts to ingest the entire project context immediately without filtering or chunking, causing it to hit the Gemini API limit on larger repositories.
To Reproduce
- Open a terminal in a project directory with a large codebase (or one containing large dependencies like
node_modulesor build artifacts). - Start the CLI:
gemini-cli - Run the command:
/conductor:setup - The operation fails with the error below.
Error Log
[API Error: {
"error": {
"message": "{\n \"error\": {\n \"code\": 400,\n \"message\": \"The input token count\n exceeds the maximum number of tokens allowed 1048576.\",\n \"status\": \"INVALID_ARGUMENT\"\n }\n}\n",
"code": 400,
"status": "Bad Request"
}
}]Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area:setupRelated to conductor:setup commandRelated to conductor:setup commandbugSomething isn't workingSomething isn't workingp1High priority. Must be fixed in the upcoming releaseHigh priority. Must be fixed in the upcoming release