# Feedback and feature requests

Warp Enterprise customers have access to dedicated support channels for reporting issues, requesting features, and getting help. This page explains how to reach the right team and provide the information needed to resolve issues quickly.

## Enterprise support channels

Enterprise customers receive **priority support** through dedicated channels:

* **Dedicated Slack or Teams channel** - Your primary support channel. A private channel shared with Warp engineers for real-time assistance, bug reports, and feature discussions.
* **Account manager** - Your direct contact for escalations, strategic feature requests, and enterprise-specific questions.

{% hint style="info" %}
For the fastest response, use your dedicated Slack or Teams channel. Warp engineers monitor these channels during business hours.
{% endhint %}

## Reporting bugs

When reporting a bug, include the following to help Warp's team investigate quickly:

1. **Description** - What happened and what you expected to happen.
2. **Steps to reproduce** - How to trigger the issue.
3. **Debugging ID** (for Agent issues) - Right-click on the Agent conversation block in question, select **Copy debugging ID**, and include it in your report. When an Agent conversation produces an error, an option to copy the debugging ID also appears inline. See [Gathering debugging ID](https://docs.warp.dev/support-and-community/troubleshooting-and-support/sending-us-feedback#gathering-ai-debugging-id) for more details.
4. **Logs** (if relevant) - See [Gathering logs](#gathering-logs) below.
5. **Environment details** - OS, Warp version, and any relevant configuration.

{% hint style="info" %}
Most Enterprise teams have user-generated content (UGC) collection disabled, which limits the diagnostic information available from debugging IDs. Logs and detailed reproduction steps are especially important for Enterprise bug reports.
{% endhint %}

### Gathering logs

Warp's logs do not contain console input or output. Log file locations by platform:

* **macOS** - `~/Library/Logs/warp.log*`
* **Windows** - `%LOCALAPPDATA%\warp\Warp\data\logs\warp.log*`
* **Linux** - `~/.local/state/warp-terminal/warp.log*`

You can also access logs directly in the app: open the **Command Palette** (`⌘P` on macOS / `Ctrl+Shift+P` on Windows/Linux) and search for **View Warp Logs**.

For detailed log gathering instructions, including how to zip logs and capture crash reports, see [Sending Feedback & Logs](https://docs.warp.dev/support-and-community/troubleshooting-and-support/sending-us-feedback).

## Requesting features

To request a new feature or enhancement:

* **Enterprise customers** - Share feature requests through your dedicated Slack/Teams channel or with your account manager. This ensures your request is tracked and prioritized by the product team.
* **Public feature requests** - Open an issue on [GitHub Issues](https://github.com/warpdotdev/warp/issues/new/choose) for visibility and community discussion.

## Specialized contacts

For security or privacy inquiries, reach out to the appropriate team directly:

* **Security issues** - <security@warp.dev>
* **Privacy questions** - <privacy@warp.dev>

For all other inquiries — including billing, technical issues, and feature requests — contact your account manager or dedicated Slack/Teams channel.

## Related resources