The Console
The Console is a real-time log of everything Curlex does — every request sent, every response received, every redirect followed, every script log output, and every error. It is the first place to look when a request is not behaving as expected.
Opening the Console
Click Console in the status bar at the bottom of the window, or press `Cmd/Ctrl + ``.
The console slides up from the bottom. Click the same button or press the shortcut again to close it.
Log Levels
The Console shows four levels of messages, each colour-coded:
| Level | Colour | What it shows |
|---|---|---|
| INFO | Blue | Each request dispatched and response received — method, URL, status code, timing |
| WARN | Yellow | Redirects followed, retries attempted, non-critical notices |
| ERROR | Red | Network failures, TLS errors, DNS failures, script exceptions |
| TRACE | Grey | Low-level details — TLS version and cipher, certificate info, raw timing values |
Use the filter button in the Console toolbar to show only the levels you care about.
Console Toolbar
| Button | What it does |
|---|---|
| Clear | Removes all current log entries |
| Copy | Copies the entire visible log to your clipboard |
| Download | Saves the log as a .log text file |
| Filter | Shows a panel to toggle which log levels are visible |
Script Output
Any console.log(), console.warn(), console.error(), or console.info() call inside a test script or pre-request script prints to the Console. This is the primary debugging tool for scripts:
// In a test script or pre-request script
console.log("Token:", fc.environment.get("authToken"));
console.log("Response body:", fc.response.text());
In the Collection Runner, script logs also appear in the Pre-request Logs tab inside each result's detail panel — you do not need the Console open to see them.
TLS and Network Details
At TRACE level, the Console shows low-level connection details for every HTTPS request:
- TLS version (TLS 1.2 or TLS 1.3)
- Cipher suite
- Peer certificate subject and issuer
- Connection timing breakdown (DNS, TCP, TLS handshake, time to first byte, download)
This is useful for debugging certificate errors, verifying that the correct TLS version is negotiated, and diagnosing slow connections.