> ## Documentation Index
> Fetch the complete documentation index at: https://docs.slomo.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Slomo CLI: timeline — Chronological Event Feed and Tail

> Print a chronological event feed for any session or issue, filter to warnings and errors only, or live-tail a running app with --follow.

`slomo timeline` prints every event in a session in chronological order. Use it for a quick read-through of what happened, or pipe it into other tools for further processing.

```
slomo timeline [REF] [OPTIONS]
```

<ParamField path="REF" type="string">
  Session id (prefix ok), issue id, or empty for the latest session.
</ParamField>

| Option           | Effect                                                             |
| ---------------- | ------------------------------------------------------------------ |
| `--follow`, `-f` | Live-tail a running session — new events print as they are written |
| `--errors`       | Only warnings and errors                                           |

```console theme={null}
$ slomo timeline
13:04:52.130  function.enter   checkout(db=…, sku='gadget')
13:04:52.133  sql.query        SELECT sku, qty FROM inventory WHERE sku = ?
13:04:52.133  sql.result       0 rows, 9µs
13:04:52.134  function.exception  TypeError: 'NoneType' object is not subscriptable
```

## Live-tailing

`--follow` watches the newest session's `timeline.jsonl` and streams events as your app writes them — run your app in one terminal, the tail in another:

```bash theme={null}
slomo timeline --follow            # everything, as it happens
slomo timeline --follow --errors   # quiet until something goes wrong
```

Because the writer batches every 0.5 s, events appear with at most that much delay.

## See also

* [Search and timeline guide](/investigating/search-and-timeline)
* `slomo issue timeline REF` — pre-scoped to an issue's latest incident ([reference](/reference/cli/issues#slomo-issue-timeline))