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.
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.

sending feedback from the macOS menu and Warp Essentials

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:

zip -j ~/Desktop/warp-logs.zip ~/Library/Logs/warp.log*

Warp Preview logs on macOS

Run the following to zip the Warp Preview logs to your Desktop:

zip -j ~/Desktop/warp_preview-logs.zip ~/Library/Logs/warp_preview.log*

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:

# Run if Warp on macOS is installed
RUST_LOG=wgpu_core=info,wgpu_hal=info /Applications/Warp.app/Contents/MacOS/stable

# Run if Warp Preview on macOS is installed
RUST_LOG=wgpu_core=info,wgpu_hal=info /Applications/WarpPreview.app/Contents/MacOS/preview

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:

Compress-Archive -Path "$env:LOCALAPPDATA\warp\Warp\data\logs\warp.log*" -DestinationPath "$([Environment]::GetFolderPath('Desktop'))\warp-logs.zip"

Warp Preview logs on Windows

Close Warp Preview and run the following from another terminal to zip the logs to your Desktop:

Compress-Archive -Path "$env:LOCALAPPDATA\warp\WarpPreview\data\logs\warp_preview.log*" -DestinationPath "$([Environment]::GetFolderPath('Desktop'))\warp_preview-logs.zip"

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:

# Run if Warp on Windows is installed for a single user
$env:RUST_LOG="wgpu_core=info,wgpu_hal=info"; & "$env:LOCALAPPDATA\Programs\Warp\warp.exe"

# Run if Warp on Windows is installed for all users
$env:RUST_LOG="wgpu_core=info,wgpu_hal=info"; & "$env:PROGRAMFILES\Warp\warp.exe"

# Run if Warp Preview on Windows is installed for a single user
$env:RUST_LOG="wgpu_core=info,wgpu_hal=info"; & "$env:LOCALAPPDATA\Programs\WarpPreview\preview.exe"

# Run if Warp Preview on Windows is installed for all users
$env:RUST_LOG="wgpu_core=info,wgpu_hal=info"; & "$env:PROGRAMFILES\WarpPreview\preview.exe"

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:

tar -czf ~/warp-logs.tar.gz -C ~/.local/state/warp-terminal warp.log*

Warp Preview logs on Linux

Run the following to zip the Warp Preview logs to your home directory:

tar -czf ~/warp_preview-logs.tar.gz -C ~/.local/state/warp-terminal-preview warp_preview.log*

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:

# Run if Warp on Linux is installed
RUST_LOG=wgpu_core=info,wgpu_hal=info MESA_DEBUG=1 EGL_LOG_LEVEL=debug warp-terminal

# Run if Warp Preview on Linux is installed
RUST_LOG=wgpu_core=info,wgpu_hal=info MESA_DEBUG=1 EGL_LOG_LEVEL=debug warp-terminal-preview

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:

files=$(find ~/Library/Logs/DiagnosticReports -name "*.ips" -exec grep -l "dev\.warp" {} + 2>/dev/null) && [ -n "$files" ] && echo "$files" | xargs zip -j ~/Desktop/warp-crash-logs.zip || echo "No Warp crash reports found."

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).

Collecting debug info on Windows

Occasionally, the Warp team may as you do provide debugging information on Windows OS in particular with one of the following:

# If Warp is in your PATH, Run:
warp --dump-debug-info

# Otherwise you may need to use an absolute path and ...
# Warp on Windows is installed for a single user, Run:
& $env:LOCALAPPDATA\programs\Warp\warp.exe --dump-debug-info

# Warp on Windows is installed for all users, Run:
& $env:PROGRAMFILES\Warp\warp.exe --dump-debug-info

Collecting CPU samples

Certain conditions can cause Warp to use more CPU than expected or become unresponsive. Collecting a CPU sample while the issue is happening is the best way to report it. The sample provides the information the Warp team needs to identify and fix the root cause.

Collect a sample using the steps for your platform and attach it to a new GitHub issue.

Reproduce the high CPU usage or unresponsiveness in Warp.
While the issue is occurring, open Activity Monitor, select the Warp process, and click Sample Process.

Sampling the Warp process in Activity Monitor

Save the resulting sample and attach it to your GitHub issue.

Install samply to record a CPU trace:

powershell -ExecutionPolicy Bypass -c "irm https://github.com/mstange/samply/releases/download/samply-v0.13.1/samply-installer.ps1 | iex"

Find the Warp process ID:
```
Get-Process *warp*
```
Start recording, replacing <PID> with the process ID from the previous step:
```
samply record -p <PID>
```
Reproduce the issue that causes high CPU usage or unresponsiveness.
Press Ctrl+C to stop recording. samply opens the profile in the Firefox Profiler in your browser. Click the upload icon in the top-right corner to generate a shareable link, then paste it into your GitHub issue.

Install samply to record a CPU trace:

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/mstange/samply/releases/download/samply-v0.13.1/samply-installer.sh | sh

samply requires access to Linux perf events. If you get a permission error, run:

echo '-1' | sudo tee /proc/sys/kernel/perf_event_paranoid

Start recording the Warp process:

samply record -p $(pgrep -f warp-terminal)

Reproduce the issue that causes high CPU usage or unresponsiveness.
Press Ctrl+C to stop recording. samply opens the profile in the Firefox Profiler in your browser. Click the upload icon in the top-right corner to generate a shareable link, then paste it into your GitHub issue.

If you prefer not to install samply, you can use the built-in perf tool instead:

perf record -g -p $(pgrep -f warp-terminal) -- sleep 30

Attach the resulting perf.data file from your current directory to your GitHub issue.

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.

PreviousOz Open Source Partnership NextKnown Issues

Last updated 1 day ago

Was this helpful?

hashtagSending Warp feedback

hashtagSubscriber and Enterprise

hashtagGathering Warp Logs

hashtagCollecting crash reports on macOS

hashtagCollecting debug info on Windows

hashtagCollecting CPU samples

hashtagGathering AI debugging ID

Sending Warp feedback

Subscriber and Enterprise

Gathering Warp Logs

Collecting crash reports on macOS

Collecting debug info on Windows

Collecting CPU samples

Gathering AI debugging ID