Skip to content

/conductor setup fails with "token count exceeds maximum" (400) on large repositories #11

@gotgelf

Description

@gotgelf

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

  1. Open a terminal in a project directory with a large codebase (or one containing large dependencies like node_modules or build artifacts).
  2. Start the CLI: gemini-cli
  3. Run the command: /conductor:setup
  4. 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"
  }
}]

Metadata

Metadata

Assignees

Labels

area:setupRelated to conductor:setup commandbugSomething isn't workingp1High priority. Must be fixed in the upcoming release

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions