Add script logs in Timeline document

debugging/timeline.mdx

@@ -1,19 +1,19 @@
 ---
 title: "Timeline"
+description: "Inspect the main request, script-triggered HTTP calls, and console output in one chronological view."
 ---
 
-The **Timeline** tab provides comprehensive insights into your API requests and responses. It displays detailed information about what was sent, what was received, and network-level details to help you debug and validate your API calls effectively.
+**Timeline** tab shows everything that happened during a request run. It includes the main HTTP call, any extra requests made from scripts, and the resolved request details for each step.
 
-## Timeline Structure
+## Timeline Interface
 
 The Timeline tab is organized into three categories:
 
 1. **Request**
 2. **Response**
 3. **Network Logs**
 
-![Response Timeline](/images/screenshots/send-request/res-data-and-cookie/res-timeline.webp)
-
+![Response Timeline](/images/screenshots/send-request/res-data-and-cookie/01-timeline.webp)
 ### 1. Request Tab
 
 The Request tab displays everything that was sent with your API request:
@@ -45,3 +45,21 @@ The Network Logs tab provides low-level network insights for advanced debugging:
 * **Debugging Information** - Additional network-level diagnostics
 
 This comprehensive view helps you identify performance bottlenecks, debug connection issues, and understand the complete lifecycle of your API requests.
+
+## Script Logs in Timeline
+
+When scripts use [`bru.sendRequest()`](/testing/script/javascript-reference#brusendrequestoptions-callback) or [`bru.runRequest()`](/testing/script/javascript-reference#brurunrequestrequestpathname), Timeline lists every HTTP call made during the run. Use the filter tabs to narrow the view.
+
+![Script Logs in Timeline](/images/screenshots/send-request/res-data-and-cookie/res-timeline.webp)
+
+The number on each tab is how many requests match that filter.
+
+| Tab | What it shows |
+| --- | --- |
+| **All** | Every HTTP request from the run including the main request plus any calls made from scripts (with or without `sendRequest` / `runRequest`). |
+| **Request** | Only the **main request** — the HTTP call defined in the request URL bar (method, URL, body, and headers you configured in Bruno). |
+| **Pre-Request** | Only HTTP requests executed during the **pre-request script** phase (from `bru.sendRequest()` or `bru.runRequest()` before the main request is sent). |
+| **Post-Response** | Only HTTP requests executed during the **post-response** or **test** script phase (from `bru.sendRequest()` or `bru.runRequest()` after the main response returns). |
+
+Click a row to expand it and inspect that call's request body, headers, response, and network timing. Use **Clear Timeline** to reset the list before the next run.
+

send-requests/res-data-cookies/res-data.mdx

@@ -2,11 +2,11 @@
 title: "Response Data"
 ---
 
 The API returns data as a response from the server after the request is executed. The response panel in Bruno provides you with an organized view of the API's response, including the body, headers, HTTP status code, raw response code, and more.
 
 ### Response Panel
 
 After executing a request, the response panel provides detailed information on the API's response. It shows the response body, headers, status code, and other relevant data. You can also search within the response using the `cmd+f` or `ctrl+f` keyboard shortcut.
 
 ![Response Panel](/images/screenshots/send-request/res-data-and-cookie/res-data.webp)
 
@@ -24,7 +24,7 @@
 
 ### Timeline
 
-The response timeline displays the response headers sent along with the request body, including details such as content-type, date, cache, and connection status.
+The **Timeline** tab lists every HTTP call from a request run along with the main request plus any calls made by scripts. See [Timeline](/debugging/timeline) for context badges (`main`, `sendRequest`, `runRequest`), filter tabs, and per-request details.
 
 ![Response Timeline](/images/screenshots/send-request/res-data-and-cookie/res-timeline.webp)
 

testing/script/javascript-reference.mdx

@@ -20,7 +20,7 @@
 | ------------------------------ | -------------------------------------------------------------------- |
 | req.getUrl()                   | Get the current request URL.                                         |
 | req.setUrl(url)                | Set the current request URL.                                         |
 | req.getHost()                  | Get the hostname from the request URL.                               |
 | req.getPath()                  | Get the path from the request URL.                                   |
 | req.getQueryString()           | Get the raw query string from the request URL.                       |
 | req.getPathParams()            | Extract path parameters using the path template.                     |
@@ -73,7 +73,7 @@
 
 ### `req.getHost()`
 
 Get the hostname from the request URL.
 
 ```javascript
 const host = req.getHost();
@@ -262,7 +262,7 @@
 
 ### `req.headerList`
 
 `req.headerList` exposes the full **PropertyList** interface for request headers, giving you richer querying, iteration, and bulk-mutation capabilities beyond the basic `getHeader` / `setHeader` methods. All key lookups are **case-insensitive** per the HTTP spec.
 
 <Info>
 `req.headerList` is available in **pre-request** and **test** scripts. Changes made via write methods take effect before the request is sent.
@@ -300,8 +300,8 @@
 | `req.headerList.has(name)` | `boolean` | `true` if any header with that key exists. |
 | `req.headerList.has(name, value)` | `boolean` | `true` if a header with that key **and** exact value exists. |
 | `req.headerList.has(object)` | `boolean` | `true` if a header matching `object.key` exists. |
 | `req.headerList.find(fn, context?)` | `object \| undefined` | First header for which the predicate returns truthy. |
 | `req.headerList.filter(fn, context?)` | `object[]` | All headers for which the predicate returns truthy. |
 | `req.headerList.indexOf(item)` | `number` | Index of a header by string key or `{ key, value }` object; `-1` if not found. |
 
 ```javascript
@@ -429,7 +429,7 @@
 
 **Parameters:**
 
 - `options` (object, optional): `raw` (boolean) — when `true`, returns the raw unparsed body string; otherwise returns the parsed object (default).
 
 ```javascript
 // Get the parsed body object (for JSON content type)
@@ -595,7 +595,7 @@
 
 ### `res.headers`
 
 A plain object containing all response headers as key-value pairs. Header names are lowercased.
 
 ```javascript
 console.log(res.headers);
@@ -689,7 +689,7 @@
 
 ### `res.getHeaders()`
 
 Returns an object containing all response headers as key-value pairs. Header names are lowercased.
 
 ```javascript
 const headers = res.getHeaders();
@@ -704,7 +704,7 @@
 
 ### `res.headerList`
 
 `res.headerList` exposes the full **PropertyList** interface for response headers, giving you richer querying and iteration capabilities beyond `getHeader` / `getHeaders`. All key lookups are **case-insensitive** per the HTTP spec.
 
 <Warning>
 `res.headerList` is **read-only**. Calling any write method (`add`, `upsert`, `remove`, `clear`, `populate`, `repopulate`, `assimilate`) throws a `"HeaderList is read-only"` error. Use `req.headerList` when you need to mutate headers.
@@ -745,8 +745,8 @@
 | `res.headerList.has(name)` | `boolean` | `true` if any response header with that key exists. |
 | `res.headerList.has(name, value)` | `boolean` | `true` if a header with that key **and** exact value exists. |
 | `res.headerList.has(object)` | `boolean` | `true` if a header matching `object.key` exists. |
 | `res.headerList.find(fn, context?)` | `object \| undefined` | First response header for which the predicate returns truthy. |
 | `res.headerList.filter(fn, context?)` | `object[]` | All response headers for which the predicate returns truthy. |
 | `res.headerList.indexOf(item)` | `number` | Index of a header by string key or `{ key, value }` object; `-1` if not found. |
 
 ```javascript
@@ -1453,7 +1453,7 @@
 </Note>
 
 <Tip>
-  You can see the executed request using `sendRequest` in the [timeline tab](/send-requests/res-data-cookies/res-data#timeline) with `sendRequest` tag attached to it.
+  You can see the executed request in the [Timeline](/debugging/timeline) tab with a `sendRequest` context badge.
 </Tip>
 
 ```javascript
@@ -1598,7 +1598,7 @@
 </Warning>
 
 <Tip>
-  You can see the executed request using `runRequest` in the [timeline tab](/send-requests/res-data-cookies/res-data#timeline) with `runRequest` tag attached to it.
+  You can see the executed request in the [Timeline](/debugging/timeline) tab with a `runRequest` context badge.
 </Tip>
 
 ```javascript