> ## Documentation Index
> Fetch the complete documentation index at: https://docs.squasher.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Send feedback to Squasher

> Report a bug, an idea, or a docs problem to the Squasher team from the dashboard, the CLI, the MCP server, or the API.

Feedback goes to the Squasher team for review. It does not go to your project, and your team does
not see it in the dashboard.

## Send feedback from the dashboard

1. Open the account menu at the bottom of the sidebar and select **Send feedback**. Or press **⌘ K**
   (**Ctrl K** on Windows and Linux) and select **Send feedback**.
2. Choose a kind: **Bug**, **Idea**, **Docs**, or **Other**.
3. Write your message and send it.

The dialog adds the URL of the page that you are on. After you send the message, it shows a receipt
ID. Give that ID to the Squasher team if you contact them about the report.

## Send feedback from the CLI

```bash theme={null}
squasher feedback "The logs page does not show the service filter." --kind bug
echo "The on-call page does not explain overrides." | squasher feedback --kind docs
```

The CLI prints `Receipt: <id>`. Add `--title`, `--page`, or `--tool` to give more context. See
[CLI reference](/integrations/cli-reference#send-feedback-to-squasher).

## Send feedback from an agent

An agent that uses the [Squasher MCP server](/integrations/mcp) calls the `feedback.submit`
operation in `execute`. An agent without MCP sends `POST https://api.squasher.ai/v1/feedback`. An
agent without a Squasher account can use the anonymous
[Feedback.now endpoints](/api-reference/feedback#send-feedback-without-an-api-key).

## What Squasher records

* The kind, the message, and the title.
* The page, tool, or client that you name in the report.
* The organization, project, and user that the credential belongs to, so the team can reply.

Do not put API keys, passwords, personal data, or telemetry payloads in feedback.

Each organization can send 100 reports an hour. After that, the API returns `429` with a
`Retry-After` header.

## Next steps

<CardGroup cols={2}>
  <Card title="Feedback API" icon="https://mintcdn.com/nextbigthingllc/eorsKshEMzXoeuUW/icons/code-bracket.svg?fit=max&auto=format&n=eorsKshEMzXoeuUW&q=85&s=a55718acc02a4969cfc6033afceae7e4" href="/api-reference/feedback" width="24" height="24" data-path="icons/code-bracket.svg">
    See the request body and the anonymous endpoints.
  </Card>

  <Card title="Troubleshooting" icon="https://mintcdn.com/nextbigthingllc/eorsKshEMzXoeuUW/icons/lifebuoy.svg?fit=max&auto=format&n=eorsKshEMzXoeuUW&q=85&s=6bbe7d806cd7af26145d093e4f104166" href="/troubleshooting" width="24" height="24" data-path="icons/lifebuoy.svg">
    Fix common setup problems.
  </Card>
</CardGroup>