# Report

`mapbox report` sends feedback about the CLI itself — a bug, a missing command, anything else — to the Mapbox CLI team. It needs no login and no extra token scope.

-   [`mapbox report`](#mapbox-report)

## `mapbox report`

Sends one message. What's sent is:

-   your message, with the CLI's version and operating system appended (`— mapbox-cli <version> on <os>`)
-   the category (`general` unless you pass `--category`)
-   a location of `0, 0`, which the API requires; the CLI sends nothing about where you are

That's the whole body: no files or command history are attached. Like every request the CLI makes, it also carries the CLI's `User-Agent`. The message is filed under a Mapbox account, not yours, so [`mapbox feedback list`](https://docs.mapbox.com/cli/reference/feedback/#mapbox-feedback-list) won't show it, and there's no way to read it back or delete it afterward. Use `--dry-run` first to see exactly what the CLI would send.

It's sent with an access token the CLI provides, so it works without a login. With `--token` or `--use-login`, or while the CLI's token can't be used (for example, it's revoked or rate-limited), it's sent with your own token instead. Either way, it's filed under Mapbox's account.

**Parameters:**

| Parameter | Description |
| --- | --- |
| `<message>` | What you want to tell the Mapbox CLI team. Required; quote it. A message starting with `-` goes after `--`, with every flag before it. |
| `--category` | What kind of feedback this is, such as `bug` or `feature_request`. Free text. Defaults to `general`. |
| `--dry-run` | Print the request this would send, and which token it would use, then exit without sending it. |

**Examples:**

```sh
mapbox report "I'd like support for optimization commands"
mapbox report "tilesets query hangs behind my proxy" --category bug
mapbox report "tilesets query hangs behind my proxy" --dry-run
mapbox report --category bug -- "-x is ignored"
```