Network Log
Logs for all network traffic (both requests and responses) originating from the current terminal session.
Last updated
Logs for all network traffic (both requests and responses) originating from the current terminal session.
Last updated
You can use Warp’s network log to help debug issues or simply use it to understand when information is sent or received over the network throughout a Warp terminal session.
Each log item is a timestamped Debug format string for either a request or response object handled by Warp. Messages are logged via pre-request and post-response hooks in Warp’s internal HTTP client.
To access the network panel from the Command Palette, type in “Show Warp Network Log”
That will insert a workflow into your input editor - it should look something like this: tail -f "some/path/to/warp_network.log".
Press Enter to run this workflow.
Then search for an AI Command Suggestion or Share a Block to see the network log activity.
Once you run one of these examples, you’ll see the corresponding requests and responses logged in the network log.
At the moment, network traffic originating from crash reports and error messages is not captured in the network log. This is due to our use of the Sentry SDK, which encapsulates all network logic and doesn’t currently expose a hook for handling requests and responses directly. The team is actively investigating a solution to include such traffic in the log in a future release. You may also disable Crash Reporting entirely in Warp’s Settings > Privacy tab.