> For the complete documentation index, see [llms.txt](https://docs.bito.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bito.ai/ai-code-reviews-in-cli/troubleshooting.md).

# Troubleshooting

Solutions to common issues when using AI Code Reviews in CLI.

#### Enable debug output

```shellscript
bitoreview review --debug
# or
bitoreview review -d
```

#### Enable verbose logging

```shellscript
bitoreview review --verbose
# or
bitoreview review -v
```

#### Common issues

**Issue: "API key not found"**

```shellscript
# Set your API key
bitoreview config set-api-key YOUR_KEY

# Verify it's set
bitoreview config show-api-key
```

**Issue: "Wingman binary not found"**

Re-run the CLI installer to reinstall wingman:

* **macOS/Linux (Terminal):**

```shellscript
curl -fsSL https://bitoreview.bito.ai/install.sh | bash
```

* **Windows (PowerShell):**

```shellscript
irm https://bitoreview.bito.ai/install.ps1 | iex
```

**Issue: Slow reviews on large codebases**

* Use `--mode essential` for faster feedback
* Focus on specific files: `bitoreview review src/changed-file.js`
* Use `--type uncommitted` to limit scope

**Issue: Too many low-priority issues**

```shellscript
# Filter to high severity only
bitoreview review --severity high

# Or use essential mode
bitoreview review --mode essential
```

#### Performance expectations

|    Codebase size    | Approximate time |
| :-----------------: | :--------------: |
|   Small (<5 files)  |   30-60 seconds  |
| Medium (5-20 files) |    1-3 minutes   |
|  Large (20+ files)  |    3-8 minutes   |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bito.ai/ai-code-reviews-in-cli/troubleshooting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.