Sending Feedback & Logs
Submit your feedback, bugs or feature requests to Warp as well as logs, debugging id, bugs, feature requests, novel ideas, etc.
Sending Warp feedback
Open a new bugs or feature request in our GitHub repository.
Join our Warp Community Slack and share feedback in #feedback-general, or #feedback-preview if it is specific to Warp Preview.
Join our Discord server, and ask questions or share feedback in
#questions-and-feedback.For security issues or questions, email [email protected].
For questions about privacy, email [email protected].
Subscriber and Enterprise
For subscriber technical issues or questions (bugs, credits, etc.), email [email protected].
For subscriber billing issues or questions (refunds, cancellation, etc.), email [email protected].
For enterprise, please direct all feedback and issues to your designated Slack Channel.

Gathering Warp Logs
You can view Warp's logs directly from inside the app by opening the Command Palette (CMD + P on macOS / CTRL + SHIFT + P on Windows/Linux) and searching for "View Warp Logs", or by selecting it from the profile menu in the top-right corner.
Alternatively, you can retrieve Warp's logs manually by following the instructions for your platform below. Locate the log file and attach it to your GitHub issue or email.
Warp's logs and crash reports do not contain any console input or output. See more on how we handle Crash Reports and Telemetry.
The Warp log files are located at ~/Library/Logs/.
Warp logs on macOS
Run the following to zip the Warp logs to your Desktop:
Warp Preview logs on macOS
Run the following to zip the Warp Preview logs to your Desktop:
If your issue is graphical (e.g. no display of windows) or a crash, please run Warp with the following command to capture more log information:
The Warp log files are located at $env:LOCALAPPDATA\warp\Warp\data\logs\.
Warp logs on Windows
Close Warp and run the following from another terminal to zip the logs to your Desktop:
Warp Preview logs on Windows
Close Warp Preview and run the following from another terminal to zip the logs to your Desktop:
If your issue is graphical (e.g. no display of windows) or a crash, please run Warp with the following command to capture more log information:
The Warp log files are located at ~/.local/state/warp-terminal/.
Warp logs on Linux
Run the following to zip the Warp logs to your home directory:
Warp Preview logs on Linux
Run the following to zip the Warp Preview logs to your home directory:
If your issue is graphical (e.g. no display of windows) or a crash, please run Warp with the following command to capture more log information:
Collecting crash reports on macOS
If Warp crashes, macOS may generate .ips crash report files in ~/Library/Logs/DiagnosticReports/. Run the following to collect all Warp crash reports into a zip on your Desktop:
Attach the resulting warp-crash-logs.zip to your bug report.
This command searches crash report files for Warp's bundle identifier, so it works across all Warp channels (Stable, Preview).
Gathering AI debugging ID
To gather the debugging ID, RIGHT-CLICK on the AI conversation block in question and select "Copy debugging ID", then paste that into the bug report that you submit so that our team can investigate the issue.
Whenever there is an error in the Agent Conversation, there will also be an option to directly copy the debugging ID for the bug report.

Last updated
Was this helpful?